delete_dns_records

THE RISK

Critical Risk

Why delete_dns_records needs a policy

DNS record deletion cannot be undone and directly impacts domain functionality. Misuse could redirect traffic, disable email services, or cause service outages. This is a destructive operation with significant blast radius, classified as high severity rather than critical because it requires matching existing record data (some guard against accidental bulk deletion) and affects only DNS records rather than data loss…

From the tool's definition Tool name explicitly states 'delete_dns_records' and description confirms it 'Delete DNS records for a domain.' This is an irreversible deletion operation.

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

POLICY

How to control delete_dns_records

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

policy.json

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

delete_dns_records 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 Spaceship 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 Spaceship MCP Server tools

Write create_a_record Create an A record (IPv4 address) for a domain Write create_aaaa_record Create an AAAA record (IPv6 address) for a domain Write create_cname_record Create a CNAME record (canonical name/alias) for a domain Write create_dns_record Create a new DNS record for a domain Write create_mx_record Create an MX record (mail exchange) for a domain Write create_srv_record Create an SRV record (service locator) for a domain Write create_txt_record Create a TXT record (text data) for a domain Write update_dns_records Update DNS records for a domain

All 10 Spaceship 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 Spaceship 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_dns_records

What does the delete_dns_records tool do? +

Delete DNS records for a domain. Requires full record data matching the existing record. It is categorised as a Destructive tool in the Spaceship 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_records? +

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

What risk level is delete_dns_records? +

delete_dns_records 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_records? +

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

Set action: deny in the PolicyLayer policy for delete_dns_records. 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_records? +

delete_dns_records is provided by the Spaceship MCP Server MCP server (mattcollins/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spaceship MCP Server tool call.

Start from Spaceship 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 →