This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-cancel-transfer.md
What dynadot_cancel_transfer does on Dynadot
AI agents call dynadot_cancel_transfer to permanently remove resources in Dynadot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why dynadot_cancel_transfer is rated Critical
Cancelling a pending domain transfer is an irreversible action — once cancelled, the transfer process is terminated and cannot be undone without initiating a completely new transfer request. This falls under Destructive as it permanently aborts an in-progress operation with no undo path.
From the tool's definition Cancel a pending transfer order
Attacks that exploit this kind of access
The rule that runs dynadot_cancel_transfer 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_cancel_transfer, this is the rule to start with:
dynadot_cancel_transfer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_cancel_transfer call is checked against it from then on.
Questions about dynadot_cancel_transfer
Cancel a pending transfer order. It is categorised as a Destructive tool in the Dynadot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_cancel_transfer: 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_cancel_transfer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dynadot_cancel_transfer 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_cancel_transfer. 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_cancel_transfer 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.
Across the catalogue