transfer_domain

Transfer a domain to your 20i account

SERVER20i MCP Server SOURCEcbrown35/20i-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/cbrown35-20i-mcp/transfer-domain.md

WHAT IT DOES

What transfer_domain does on 20i MCP Server

AI agents use transfer_domain to create or update resources in 20i MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 20i MCP Server environment.

RISK

Why transfer_domain is rated Medium

Transferring a domain moves it into a new registrar account, which is a significant write/modification action with lasting consequences (changes registrar control, may lock the domain during transfer, incurs fees). It is not purely destructive (the domain still exists) but is high severity due to the difficulty of reversal and potential financial implications (transfer fees).

From the tool's definition "Transfer a domain to your 20i account" — initiates a domain transfer operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_domain safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_domain, this is the rule to start with:

transfer_domain Rate-limited

transfer_domain 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": {
    "transfer_domain": {
      "limits": [
        {
          "counter": "transfer_domain_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 20i MCP Server, apply this rule, and every transfer_domain call is checked against it from then on.

FAQ

Questions about transfer_domain

What does the transfer_domain tool do? +

Transfer a domain to your 20i account. It is categorised as a Write tool in the 20i MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on transfer_domain? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for transfer_domain: 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 20i MCP Server. Nothing to install.

What risk level is transfer_domain? +

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

Can I rate-limit transfer_domain? +

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

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

transfer_domain is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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