dns_report
Fetch the DNS Report for a given zone since a date
This record as markdown: /tools/cloudflare/dns-report.md
What dns_report does on Cloudflare
AI agents call dns_report to retrieve information from Cloudflare without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dns_report is rated Low
This tool retrieves historical DNS report data for a Cloudflare zone. The verb 'Fetch' and the absence of any modification language (create, update, delete, execute) confirm this is a read operation. The severity is low because it only accesses existing report data without side effects, and the blast radius of misuse (e.g., an AI agent fetching DNS reports) is limited to information disclosure.
From the tool's definition 'Fetch the DNS Report' indicates a read-only retrieval operation with no modification or execution of external systems.
Attacks that exploit this kind of access
The rule that runs dns_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_report, this is the rule to start with:
dns_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every dns_report call is checked against it from then on.
Questions about dns_report
Fetch the DNS Report for a given zone since a date. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for dns_report: 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. Nothing to install.
dns_report 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 dns_report 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 dns_report. 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.
dns_report is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cloudflare, and thousands of servers like it.
This server
Across the catalogue