Missing Bulk Management Features for IP Lists

### What versions & operating system are you using?

### Please provide a link to a minimal reproduction

https://github.com/cloudflare/cloudflare-docs

### Describe the Bug

Dear Cloudflare Support Team,

I would like to report a major usability issue with the current IP Lists management interface in Cloudflare.

At the moment, several essential bulk-management features are missing, which makes working with large IP lists extremely slow and inefficient.

For example, in Rules / Lists / IP Lists, we urgently need the following functionality:

Export All IPs from a list, preferably to CSV, TXT, or another standard format.
Select All Items, not only the 25 IP addresses currently visible on the page.
Delete All Selected IPs at Once, including hundreds or thousands of entries across multiple pages.
An option to choose the number of rows displayed per page, for example:
25
50
100
250
500
Ideally, an option to display the entire list when technically possible.
Clear information showing the total number of IP addresses contained in the list.

Currently, only around 25 IPs are displayed per page, and bulk actions appear to apply only to those visible entries. If a list contains hundreds or thousands of IP addresses, deleting or managing them page by page wastes an enormous amount of time.

These are basic administrative features that are expected in a modern enterprise security platform, especially for customers managing large firewall and access-control datasets.

Please treat this as an urgent product and UI/UX improvement request and escalate it to the appropriate Product Management, UI/UX, and Engineering teams.

I have attached a screenshot showing the current IP List interface for reference.

Thank you, and I would appreciate confirmation that this feedback has been escalated internally.

Kind regards,
George

### Please provide any relevant error logs

_No response_

The issue identifies the IP Lists management interface and links cloudflare-docs as the reproduction, but it names no workers-sdk file, test, or entry point. First confirm whether this request belongs in workers-sdk; the requested bulk selection, export, deletion, pagination, and total-count behavior would need a defined product scope before implementation can be considered done.

Written by the indexing model from the issue text.