Delete a specific DNS record
AI agents call delete_dns_record 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.
DNS records are critical infrastructure components. Deleting a DNS record cannot be undone without manual restoration and will immediately disrupt DNS resolution for affected domains, potentially taking services offline. This constitutes a destructive action with significant blast radius.
From the tool's definition Tool name is 'delete_dns_record' and description states 'Delete a specific DNS record'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a specific DNS record. 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_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 Dns. Nothing to install.
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.
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.
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.
delete_dns_record 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 →