dynadot_add_backorder_request

Place a backorder on an expiring domain.

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

Questions about dynadot_add_backorder_request

What does the dynadot_add_backorder_request tool do? +

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.

How do I enforce a policy on dynadot_add_backorder_request? +

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.

What risk level is dynadot_add_backorder_request? +

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

Can I rate-limit dynadot_add_backorder_request? +

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.

How do I block dynadot_add_backorder_request completely? +

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.

What MCP server provides dynadot_add_backorder_request? +

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.

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