dynadot_delete_ns

Delete a nameserver record.

SERVERDynadot SOURCEeyalm321/dynadot-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-delete-ns.md

What dynadot_delete_ns does on Dynadot

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

Why dynadot_delete_ns is rated Critical

Deleting nameserver records is a destructive operation that cannot be undone without manual restoration. Misuse could remove all nameservers from a domain, rendering it unable to resolve and breaking all services depending on that domain. This has high blast radius for domain availability and is more severe than write operations. Confidence is very high because the description explicitly states 'Delete.'

From the tool's definition Tool name 'dynadot_delete_ns' and description 'Delete a nameserver record' — the verb 'delete' indicates irreversible removal of DNS infrastructure data.

Questions about dynadot_delete_ns

What does the dynadot_delete_ns tool do? +

Delete a nameserver record. It is categorised as a Destructive tool in the Dynadot 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 dynadot_delete_ns? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_delete_ns: 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 Dynadot. Nothing to install.

What risk level is dynadot_delete_ns? +

dynadot_delete_ns 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 dynadot_delete_ns? +

Yes. Add a rate_limit block to the dynadot_delete_ns 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 dynadot_delete_ns completely? +

Set action: deny in the PolicyLayer policy for dynadot_delete_ns. 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 dynadot_delete_ns? +

dynadot_delete_ns is provided by the Dynadot MCP server (eyalm321/dynadot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Dynadot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Dynadot's. Pull the full record:

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.