transfer_domain_in · Domain Suite MCP: Risk & Policy

WHAT IT DOES

What transfer_domain_in does on Domain Suite

AI agents use transfer_domain_in to create or update resources in Domain Suite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Domain Suite environment.

WHY IT NEEDS A POLICY

Why transfer_domain_in needs a policy

Initiating an inbound domain transfer creates a new domain registration/ownership record by moving a domain from another registrar. This is a Write operation (creating/modifying domain ownership state) rather than Destructive since it doesn't delete data, but it carries high severity because domain transfers are difficult to reverse, can take days, involve authorization codes, and could result in loss of control…

From the tool's definition Initiate inbound domain transfer

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_domain_in Rate-limited

transfer_domain_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": {
    "transfer_domain_in": {
      "limits": [
        {
          "counter": "transfer_domain_in_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Domain Suite, so you can run agents against it safely.

FAQ

Questions about transfer_domain_in

What does the transfer_domain_in tool do? +

Initiate inbound domain transfer. It is categorised as a Write tool in the Domain Suite 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_in? +

Register the Domain Suite MCP server in PolicyLayer and add a rule for transfer_domain_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 Domain Suite. Nothing to install.

What risk level is transfer_domain_in? +

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

Can I rate-limit transfer_domain_in? +

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

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

transfer_domain_in is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.