dynadot_set_default_ns

Set default nameservers for new domains (up to 13).

SERVERDynadot SOURCEeyalm321/dynadot-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about dynadot_set_default_ns

What does the dynadot_set_default_ns tool do? +

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.

How do I enforce a policy on dynadot_set_default_ns? +

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.

What risk level is dynadot_set_default_ns? +

dynadot_set_default_ns is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dynadot_set_default_ns? +

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.

How do I block dynadot_set_default_ns completely? +

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.

What MCP server provides dynadot_set_default_ns? +

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.

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