dynadot_domain_info
Get full details for a single domain (settings, contacts, status). IDN auto-punycoded.
This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-domain-info.md
What dynadot_domain_info does on Dynadot
AI agents call dynadot_domain_info 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.
Why dynadot_domain_info is rated Low
This tool queries and returns information about a domain without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves domain metadata. The 'low' severity reflects minimal blast radius — an agent misusing this tool could only over-query or access unauthorized domain details, but cannot cause financial harm, execute code, or destroy data.
From the tool's definition Tool description states 'Get full details for a single domain (settings, contacts, status)' — explicitly a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs dynadot_domain_info 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_domain_info, this is the rule to start with:
dynadot_domain_info is read-only, so it stays allowed. 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_domain_info call is checked against it from then on.
Questions about dynadot_domain_info
Get full details for a single domain (settings, contacts, status). IDN auto-punycoded. It is categorised as a Read tool in the Dynadot MCP Server, which means it retrieves data without modifying state.
Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_domain_info: 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_domain_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dynadot_domain_info 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_domain_info. 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_domain_info 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