Delete a DNS domain and ALL its associated records
AI agents call delete_dns_domain to permanently remove resources in Vultr Dns — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a DNS domain and all associated records) with no undo mechanism. The mass deletion of all records tied to a domain elevates the blast radius beyond a single record deletion. While not financial, the permanent loss of DNS configuration for an entire domain could cause significant operational damage if misused by an AI agent.
From the tool's definition The tool is explicitly described as 'Delete a DNS domain and ALL its associated records' — the word 'Delete' combined with 'ALL' indicates irreversible removal of data at scale.
Attacks that exploit this kind of access
Delete a DNS domain and ALL its associated records. It is categorised as a Destructive tool in the Vultr Dns MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vultr Dns MCP server in PolicyLayer and add a rule for delete_dns_domain: 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 Dns. Nothing to install.
delete_dns_domain is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_dns_domain 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.
Set action: deny in the PolicyLayer policy for delete_dns_domain. 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.
delete_dns_domain is provided by the Vultr Dns MCP server (rsp2k/vultr-dns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →