Delete a DNS record from a Cloudflare zone.
AI agents call cloudflare_delete_dns_record to permanently remove resources in Integrations MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
DNS record deletion is an irreversible operation that cannot be undone without manual intervention. If misused by an AI agent, it could disrupt domain routing, email delivery, SSL certificate validation, and other critical infrastructure depending on that DNS record. This causes direct operational harm and qualifies as Destructive (most severe applicable category).
From the tool's definition Tool name and description explicitly state 'Delete a DNS record from a Cloudflare zone.' The verb 'delete' combined with DNS record management indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a DNS record from a Cloudflare zone. It is categorised as a Destructive tool in the Integrations MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Integrations MCP server in PolicyLayer and add a rule for cloudflare_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 Integrations MCP. Nothing to install.
cloudflare_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 cloudflare_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 cloudflare_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.
cloudflare_delete_dns_record 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 →