dynadot_server_list

List all nameservers in the account (paginated).

SERVERDynadot SOURCEeyalm321/dynadot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-server-list.md

WHAT IT DOES

What dynadot_server_list does on Dynadot

AI agents call dynadot_server_list to retrieve information from Dynadot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why dynadot_server_list is rated Low

This tool retrieves and displays existing nameserver data from the account without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query operation with minimal blast radius—unauthorized listing of nameservers poses low risk to the account itself, though it could expose infrastructure information.

From the tool's definition Tool name 'dynadot_server_list' and description 'List all nameservers in the account (paginated)' indicates a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dynadot_server_list 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_server_list, this is the rule to start with:

dynadot_server_list Allowed

dynadot_server_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynadot_server_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_server_list call is checked against it from then on.

FAQ

Questions about dynadot_server_list

What does the dynadot_server_list tool do? +

List all nameservers in the account (paginated). It is categorised as a Read tool in the Dynadot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dynadot_server_list? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_server_list: 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_server_list? +

dynadot_server_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dynadot_server_list? +

Yes. Add a rate_limit block to the dynadot_server_list 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_server_list completely? +

Set action: deny in the PolicyLayer policy for dynadot_server_list. 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_server_list? +

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

KEEP EXPLORING

More on Dynadot, and thousands of servers like it.

This server

All 105 Dynadot tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →