delete_dns_record

Delete a DNS record. On GoDaddy, deletes ALL records of same type+name (API limitation).

Server Domain Suite oso95/domain-suite-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_dns_record does on Domain Suite

AI agents call delete_dns_record to permanently remove resources in Domain Suite — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_dns_record needs a policy

This tool permanently removes DNS records without the ability to undo the action. DNS records are critical infrastructure for domain functionality (routing, mail delivery, DNSSEC, etc.). Deleting them can cause immediate outages and service disruption. The bulk deletion behavior on GoDaddy ('ALL records of same type+name') amplifies the destructive potential.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a DNS record' with the caveat that it 'deletes ALL records of same type+name' on GoDaddy, indicating irreversible removal of data.

Risk signalsBulk/mass operation — affects multiple targets

Questions about delete_dns_record

What does the delete_dns_record tool do? +

Delete a DNS record. On GoDaddy, deletes ALL records of same type+name (API limitation). It is categorised as a Destructive tool in the Domain Suite 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 Domain Suite 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 Domain Suite. 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 Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.