cloudflare_list_zones
AI agents call cloudflare_list_zones to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' verb indicates a retrieval operation that queries Cloudflare zones without modifying, deleting, or executing anything. This is a Read operation with low blast radius—even if misused, it only exposes metadata about which zones exist in the account, not their configurations or data. The empty description lowers confidence slightly, but the verb semantics are clear.
From the tool's definition Tool name 'cloudflare_list_zones' follows the 'list_*' pattern, which is a standard Read operation that retrieves data without side effects. No description provided, but the naming convention is unambiguous.
Attacks that exploit this kind of access
cloudflare_list_zones. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for cloudflare_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 Integrations MCP. Nothing to install.
cloudflare_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 cloudflare_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 cloudflare_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.
cloudflare_list_zones is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →