arvan_delete_dns_record
Delete a DNS record by id.
This record as markdown: /tools/dwin-gharibi-arvancloud-mcp/arvan-delete-dns-record.md
What arvan_delete_dns_record does on ArvanCloud MCP Server
AI agents call arvan_delete_dns_record to permanently remove resources in ArvanCloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why arvan_delete_dns_record is rated Critical
This tool permanently removes DNS records, which cannot be undone and would disrupt domain resolution services. DNS records are critical infrastructure; deleting them could cause widespread outages. While not directly financial, the blast radius of accidental deletion (e.g., deleting a production domain's A record) is severe.
From the tool's definition Tool name is 'arvan_delete_dns_record' and description states 'Delete a DNS record by id.' The verb 'delete' combined with DNS record management indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs arvan_delete_dns_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ArvanCloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arvan_delete_dns_record, this is the rule to start with:
arvan_delete_dns_record is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ArvanCloud MCP Server, apply this rule, and every arvan_delete_dns_record call is checked against it from then on.
Questions about arvan_delete_dns_record
Delete a DNS record by id. It is categorised as a Destructive tool in the ArvanCloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ArvanCloud MCP Server MCP server in PolicyLayer and add a rule for arvan_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 ArvanCloud MCP Server. Nothing to install.
arvan_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 arvan_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 arvan_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.
arvan_delete_dns_record is provided by the ArvanCloud MCP Server MCP server (dwin-gharibi/arvancloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ArvanCloud MCP Server, and thousands of servers like it.
Across the catalogue