dynadot_set_default_ns
Set default nameservers for new domains (up to 13).
This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-set-default-ns.md
What dynadot_set_default_ns does on Dynadot
AI agents use dynadot_set_default_ns to create or update resources in Dynadot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynadot environment.
Why dynadot_set_default_ns is rated Medium
This tool creates or modifies account-level DNS configuration that persists across multiple domains. While it does not delete data and does not move money, it writes configuration that affects domain behavior. The high severity is justified because misconfiguration of nameservers could redirect domains to attacker-controlled infrastructure, disrupting services and enabling phishing or interception attacks.
From the tool's definition "Set default nameservers for new domains" - this modifies DNS configuration settings that will apply to future domain registrations, creating a persistent change to account defaults.
Attacks that exploit this kind of access
The rule that runs dynadot_set_default_ns 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_set_default_ns, this is the rule to start with:
dynadot_set_default_ns stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_set_default_ns call is checked against it from then on.
Questions about dynadot_set_default_ns
Set default nameservers for new domains (up to 13). It is categorised as a Write tool in the Dynadot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_set_default_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.
dynadot_set_default_ns is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dynadot_set_default_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.
Set action: deny in the PolicyLayer policy for dynadot_set_default_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.
dynadot_set_default_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.
This server
Across the catalogue