dynadot_add_backorder_request
Place a backorder on an expiring domain.
This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-add-backorder-request.md
What dynadot_add_backorder_request does on Dynadot
AI agents use dynadot_add_backorder_request 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_add_backorder_request is rated Medium
Backordering a domain is a reversible write operation that creates a new record in the user's backorder list. It commits a financial intent (potential future domain acquisition costs) but does not immediately transfer funds or make irreversible changes.
From the tool's definition Tool description states 'Place a backorder on an expiring domain' — this is a create operation that modifies account state by adding a new backorder request record. The Dynadot API context confirms this is a write operation affecting domain management data.
Attacks that exploit this kind of access
The rule that runs dynadot_add_backorder_request 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_add_backorder_request, this is the rule to start with:
dynadot_add_backorder_request 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_add_backorder_request call is checked against it from then on.
Questions about dynadot_add_backorder_request
Place a backorder on an expiring 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_add_backorder_request: 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_add_backorder_request 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_add_backorder_request 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_add_backorder_request. 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_add_backorder_request 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