cloudflare_list_dns_records
AI agents call cloudflare_list_dns_records 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 DNS record information from Cloudflare, which is a read-only query operation. However, DNS records are sensitive infrastructure configuration data; unauthorized access or disclosure could enable DNS spoofing, subdomain hijacking, or reconnaissance for further attacks. Severity is medium due to the information disclosure risk and potential for attack preparation, despite the read-only nature.
From the tool's definition Tool name 'cloudflare_list_dns_records' indicates a listing/query operation that retrieves DNS records. The 'list' verb is characteristic of Read operations that fetch data without side effects.
Attacks that exploit this kind of access
cloudflare_list_dns_records. 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_dns_records: 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_dns_records 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_dns_records 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_dns_records. 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_dns_records 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 →