Critical Risk →

delete_dns_record

Delete a specific DNS record

How to control delete_dns_record ↓

What delete_dns_record does on Vultr MCP

AI agents call delete_dns_record to permanently remove resources in Vultr MCP — 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

DNS records are critical infrastructure; deleting one cannot be undone without manual restoration. This is irreversible data destruction affecting domain resolution, making it the most severe category. High severity because misconfiguration could cause service outages or enable attackers to hijack domain routing. Confidence is high due to unambiguous 'delete' semantics in both name and description.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a specific DNS record' — this irreversibly removes DNS configuration data.

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 Vultr MCP, 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 Vultr MCP — 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 specific DNS record. It is categorised as a Destructive tool in the Vultr MCP 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 Vultr 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 Vultr MCP. 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 Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vultr MCP tool call.

Start from Vultr MCP, 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.

284 Vultr MCP 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.