dynadot_clear_domain_setting
Reset a specific domain setting (forwarding, dns, ns, etc.) to defaults.
This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-clear-domain-setting.md
What dynadot_clear_domain_setting does on Dynadot
AI agents call dynadot_clear_domain_setting 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_clear_domain_setting is rated Critical
Clearing/resetting domain settings (DNS, nameservers, forwarding) overwrites existing configuration irreversibly — the previous settings are lost and the domain reverts to defaults. This can cause service outages (DNS resolution failures, email disruption, website downtime) and the original configuration is not preserved, making it a destructive action with high blast radius.
From the tool's definition Reset a specific domain setting (forwarding, dns, ns, etc.) to defaults
Attacks that exploit this kind of access
The rule that runs dynadot_clear_domain_setting 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_clear_domain_setting, this is the rule to start with:
dynadot_clear_domain_setting 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_clear_domain_setting call is checked against it from then on.
Questions about dynadot_clear_domain_setting
Reset a specific domain setting (forwarding, dns, ns, etc.) to defaults. 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_clear_domain_setting: 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_clear_domain_setting 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_clear_domain_setting 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_clear_domain_setting. 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_clear_domain_setting 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