New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

infra.cloudflare.dns_delete

⚡ ACTION: Delete a DNS record from a Cloudflare zone by record ID. Removes the record immediately (Cloudflare)

SERVERApibase SOURCEapibase-mcp-client
Critical RISK CLASS
Category Destructive
Parameters 22 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about infra.cloudflare.dns_delete

What does the infra.cloudflare.dns_delete tool do? +

⚡ 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.

What parameters does infra.cloudflare.dns_delete accept? +

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.

How do I enforce a policy on infra.cloudflare.dns_delete? +

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.

What risk level is infra.cloudflare.dns_delete? +

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.

Can I rate-limit infra.cloudflare.dns_delete? +

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.

How do I block infra.cloudflare.dns_delete completely? +

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.

What MCP server provides infra.cloudflare.dns_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.