Critical Risk →

delete_dns_record

Delete a DNS zone record by line number

How to control delete_dns_record ↓

What delete_dns_record does on cPanel MCP Server

AI agents call delete_dns_record to permanently remove resources in cPanel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_dns_record needs a policy

This tool irreversibly removes DNS zone records by line number. Deleting DNS records can cause immediate service outages (e.g., mail delivery failures, website inaccessibility, broken subdomains) and cannot be undone without manual restoration or from backups. This qualifies as Destructive rather than Write.

From the tool's definition Tool name is 'delete_dns_record' and description explicitly states 'Delete a DNS zone record'. DNS records are critical infrastructure that cannot be easily recovered once deleted, and deletion is irreversible.

Documented attack patterns abuse exactly the kind of access delete_dns_record gives an agent:

How to control delete_dns_record

PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dns_record:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_dns_record"
  ]
}

delete_dns_record disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register cPanel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_dns_record

What does the delete_dns_record tool do? +

Delete a DNS zone record by line number. It is categorised as a Destructive tool in the cPanel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_dns_record? +

Register the cPanel MCP Server 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 cPanel MCP Server. Nothing to install.

What risk level is delete_dns_record? +

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.

Can I rate-limit delete_dns_record? +

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.

How do I block delete_dns_record completely? +

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.

What MCP server provides delete_dns_record? +

delete_dns_record is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every cPanel MCP Server tool call.

Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.