infra.cloudflare.dns_delete
⚡ ACTION: Delete a DNS record from a Cloudflare zone by record ID. Removes the record immediately (Cloudflare)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.cloudflare.dns-delete.md
What infra.cloudflare.dns_delete does on Apibase
AI agents call infra.cloudflare.dns_delete to permanently remove resources in Apibase, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
zone_id | string | Yes | Cloudflare Zone ID |
record_id | string | Yes | DNS record ID to delete (from dns_list results) |
Parameters from the server's own tool schema.
Why infra.cloudflare.dns_delete is rated Critical
Irreversibly deletes DNS records; misconfigured deletion could cause service outages.
From the tool's definition Delete a DNS record...Removes the record immediately
Attacks that exploit this kind of access
The rule that runs infra.cloudflare.dns_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.cloudflare.dns_delete, this is the rule to start with:
infra.cloudflare.dns_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.cloudflare.dns_delete call is checked against it from then on.
Questions about infra.cloudflare.dns_delete
⚡ ACTION: Delete a DNS record from a Cloudflare zone by record ID. Removes the record immediately (Cloudflare). It is categorised as a Destructive tool in the Apibase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
infra.cloudflare.dns_delete accepts 2 parameters: zone_id, record_id. Required: zone_id, record_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for infra.cloudflare.dns_delete: 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 Apibase. Nothing to install.
infra.cloudflare.dns_delete 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 infra.cloudflare.dns_delete 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 infra.cloudflare.dns_delete. 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.
infra.cloudflare.dns_delete is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue