Permanently delete a DNS record from a zone. e.g., zone_id
AI agents call delete_dns_record to permanently remove resources in Cloudflare Control — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting DNS records is a destructive operation that irreversibly removes infrastructure configuration. While not as severe as deleting an entire zone or database, removing DNS records can cause immediate service disruption (e.g., email delivery failure, website unavailability) depending on which records are deleted.
From the tool's definition Tool description states 'Permanently delete a DNS record' — the word 'Permanently' and the verb 'delete' are explicit markers of irreversible data destruction. This cannot be undone without manual re-creation.
Attacks that exploit this kind of access
Permanently delete a DNS record from a zone. e.g., zone_id. It is categorised as a Destructive tool in the Cloudflare Control MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cloudflare Control MCP server in PolicyLayer and add a rule for delete_dns_record: 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 Control. Nothing to install.
delete_dns_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_dns_record 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 delete_dns_record. 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.
delete_dns_record is provided by the Cloudflare Control MCP server (josephtandle/cloudflare-mcp-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 →