delete_dnssec_record

THE RISK

Critical Risk

Why delete_dnssec_record needs a policy

This tool permanently removes DNSSEC records from a domain's registry configuration. DNSSEC deletion is irreversible and could compromise domain security if executed unintentionally. The high severity reflects that removing DNSSEC protection from a domain could expose it to DNS spoofing attacks, making this a critical infrastructure risk, though not as severe as deleting the domain itself or financial transactions.

From the tool's definition Tool name is 'delete_dnssec_record' and description states it 'Deletes a DNSSEC record'. The verb 'Deletes' indicates irreversible removal of data.

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

POLICY

How to control delete_dnssec_record

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_dnssec_record"
  ]
}

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

Create a free account and register Porkbun MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Porkbun MCP Server tools

Destructive delete_dns_record Removes a specific DNS record using its ID. Destructive delete_dns_record_by_name_type Deletes all DNS records matching a domain, subdomain (optional), and type. Corresponds to Destructive delete_url_forward Deletes a URL forward record for a domain by its ID. Write add_url_forward Adds URL forwarding for a domain or subdomain. Write create_dns_record Adds a new DNS record to a specified domain. Write create_dnssec_record Creates a DNSSEC record at the registry for the domain. Write edit_dns_record Modifies an existing DNS record using its ID. Write edit_dns_record_by_name_type Edits all DNS records matching a domain, subdomain (optional), and type. Corresponds to en

All 20 Porkbun MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Porkbun MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_dnssec_record

What does the delete_dnssec_record tool do? +

Deletes a DNSSEC record associated with the domain at the registry by Key Tag. It is categorised as a Destructive tool in the Porkbun 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_dnssec_record? +

Register the Porkbun MCP Server MCP server in PolicyLayer and add a rule for delete_dnssec_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 Porkbun MCP Server. Nothing to install.

What risk level is delete_dnssec_record? +

delete_dnssec_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_dnssec_record? +

Yes. Add a rate_limit block to the delete_dnssec_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_dnssec_record completely? +

Set action: deny in the PolicyLayer policy for delete_dnssec_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_dnssec_record? +

delete_dnssec_record is provided by the Porkbun MCP Server MCP server (miraclebakelaser/porkbun-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 Porkbun MCP Server tool call.

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

CHECK YOUR STACK →