cloudflare_read_document
AI agents call cloudflare_read_document to retrieve information from Cloudflare WAF MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention 'cloudflare_read_document' clearly indicates a retrieval operation. Despite the empty description, the tool appears designed to fetch or retrieve documentation content—a non-destructive, informational operation. It causes no modifications to WAF rules, configurations, or other resources.
From the tool's definition Tool name 'cloudflare_read_document' indicates a read operation. Description is empty, limiting confidence, but the verb 'read' and context (among tools like 'list_document_names') strongly suggest data retrieval with no side effects.
Attacks that exploit this kind of access
cloudflare_read_document. It is categorised as a Read tool in the Cloudflare WAF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare WAF MCP Server MCP server in PolicyLayer and add a rule for cloudflare_read_document: 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 WAF MCP Server. Nothing to install.
cloudflare_read_document 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_read_document 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_read_document. 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_read_document is provided by the Cloudflare WAF MCP Server MCP server (quareth/cloudflare_waf_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 →