This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-grace-delete.md
What dynadot_grace_delete does on Dynadot
AI agents call dynadot_grace_delete 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_grace_delete is rated Critical
Domain deletion is irreversible and represents loss of a valuable asset. This falls under the Destructive category as it permanently removes data that cannot be easily recovered. Severity is high because domains are critical infrastructure and business assets; misuse could result in loss of DNS service, email, and web presence.
From the tool's definition Tool name 'dynadot_grace_delete' and description 'Delete a domain that' indicate irreversible deletion of a domain resource. The incomplete description cuts off but 'Delete' combined with domain management context clearly signals a destructive operation.
Attacks that exploit this kind of access
The rule that runs dynadot_grace_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dynadot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dynadot_grace_delete, this is the rule to start with:
dynadot_grace_delete 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 Dynadot, apply this rule, and every dynadot_grace_delete call is checked against it from then on.
Questions about dynadot_grace_delete
Delete a domain that. 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.
Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_grace_delete: 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.
dynadot_grace_delete 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 dynadot_grace_delete 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 dynadot_grace_delete. 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.
dynadot_grace_delete 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.
Across the catalogue