Delete a CloudFlare zone
AI agents call cf_delete_zone to permanently remove resources in Cargoshipper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a CloudFlare zone destroys all DNS records, routing configuration, and domain management for that zone irreversibly. This cannot be undone and would cause immediate service outages for any domains relying on that zone. The blast radius is critical—an AI agent with access to this tool could disable entire websites or services. This is the most severe category applicable.
From the tool's definition Tool name is 'cf_delete_zone' and description states 'Delete a CloudFlare zone'. The verb 'delete' combined with the scope (an entire DNS zone) indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a CloudFlare zone. It is categorised as a Destructive tool in the Cargoshipper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cargoshipper MCP server in PolicyLayer and add a rule for cf_delete_zone: 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 Cargoshipper. Nothing to install.
cf_delete_zone 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 cf_delete_zone 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 cf_delete_zone. 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.
cf_delete_zone is provided by the Cargoshipper MCP server (scarr7981/cargoshipper-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 →