dynadot_clear_domain_setting

Reset a specific domain setting (forwarding, dns, ns, etc.) to defaults.

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-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

Questions about dynadot_clear_domain_setting

What does the dynadot_clear_domain_setting tool do? +

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.

How do I enforce a policy on dynadot_clear_domain_setting? +

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.

What risk level is dynadot_clear_domain_setting? +

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.

Can I rate-limit dynadot_clear_domain_setting? +

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.

How do I block dynadot_clear_domain_setting completely? +

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.

What MCP server provides dynadot_clear_domain_setting? +

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.

// 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.