List all zones (domains) in the Cloudflare account.
AI agents call list_zones to retrieve information from Cloudflare MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about existing zones without modifying, deleting, or executing operations. It is a straightforward read operation with minimal security impact—an AI agent listing zones cannot cause damage, though the resulting information could inform subsequent operations. Severity is low because the action itself is non-destructive, though access control to view zones should still be enforced.
From the tool's definition Tool name 'list_zones' and description 'List all zones (domains) in the Cloudflare account' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all zones (domains) in the Cloudflare account. It is categorised as a Read tool in the Cloudflare MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP Server MCP server in PolicyLayer and add a rule for list_zones: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cloudflare MCP Server. Nothing to install.
list_zones is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_zones rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_zones. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_zones is provided by the Cloudflare MCP Server MCP server (ry-ops/cloudflare-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →