This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-set-hosting.md
What dynadot_set_hosting does on Dynadot
AI agents use dynadot_set_hosting 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_hosting is rated Medium
This tool modifies domain hosting configuration, which is a write operation that changes domain state. The severity is medium because incorrect hosting settings could disrupt domain service availability, but the change is reversible and does not involve financial transactions, destructive deletion, or arbitrary code execution. The financial impact is indirect and secondary to the core write operation.
From the tool's definition Tool name 'dynadot_set_hosting' and description 'Set the hosting type for a domain' indicate modification of domain configuration settings. This is a reversible change to existing domain data.
Attacks that exploit this kind of access
The rule that runs dynadot_set_hosting 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_hosting, this is the rule to start with:
dynadot_set_hosting 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_hosting call is checked against it from then on.
Questions about dynadot_set_hosting
Set the hosting type for a domain. 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_hosting: 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_hosting 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_hosting 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_hosting. 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_hosting 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