dynadot_transfer_in

Initiate a transfer of a domain to Dynadot.

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-transfer-in.md

WHAT IT DOES

What dynadot_transfer_in does on Dynadot

AI agents use dynadot_transfer_in 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.

RISK

Why dynadot_transfer_in is rated Medium

Initiating a domain transfer creates a new transfer request and moves a domain between registrars. This is a Write operation (reversible in that transfers can be cancelled during the transfer window), but carries high severity because domain ownership/control changes are significant and mistakes can disrupt services or result in loss of domain control.

From the tool's definition Initiate a transfer of a domain to Dynadot

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dynadot_transfer_in 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_transfer_in, this is the rule to start with:

dynadot_transfer_in Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynadot_transfer_in": {
      "limits": [
        {
          "counter": "dynadot_transfer_in_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_transfer_in call is checked against it from then on.

FAQ

Questions about dynadot_transfer_in

What does the dynadot_transfer_in tool do? +

Initiate a transfer of a domain to Dynadot. 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_transfer_in? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_transfer_in: 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_transfer_in? +

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

Can I rate-limit dynadot_transfer_in? +

Yes. Add a rate_limit block to the dynadot_transfer_in 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_transfer_in completely? +

Set action: deny in the PolicyLayer policy for dynadot_transfer_in. 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_transfer_in? +

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

KEEP EXPLORING

More on Dynadot, and thousands of servers like it.

This server

All 105 Dynadot tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →