Get details of a specific Cloudflare zone.
AI agents call cloudflare_get_zone 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.
This tool retrieves information about a Cloudflare DNS zone configuration. The verb 'Get' and the read-only nature of querying zone details (DNS records, SSL settings, etc.) without modifying them classifies this as a Read operation. The severity is low because exposure of zone configuration details has limited blast radius compared to tools that can modify DNS records, delete zones, or execute operations.
From the tool's definition Tool name 'cloudflare_get_zone' and description 'Get details of a specific Cloudflare zone' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific Cloudflare zone. 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_get_zone: 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_get_zone 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_get_zone 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_get_zone. 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_get_zone 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 →