domains_acceptIncomingDomainMoveV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-acceptincomingdomainmovev1.md

WHAT IT DOES

What domains_acceptIncomingDomainMoveV1 does on Hostinger Api

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

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name
`domain_contacts`	object	Yes	WHOIS profiles of the accepting account. Only the contact types required by the TLD are applied, but all four IDs must be provided.

Parameters from the server's own tool schema.

RISK

Why domains_acceptIncomingDomainMoveV1 is rated Medium

This tool modifies domain registration state by accepting a domain transfer and updating domain contacts (WHOIS profiles). While not immediately completing the transfer, it initiates an irreversible process that changes domain ownership. This is a reversible modification of domain metadata and contacts (Write) rather than destructive deletion.

From the tool's definition Tool performs 'Accept an incoming move for a specified domain' with requirement to provide contact profiles.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs domains_acceptIncomingDomainMoveV1 safely

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

domains_acceptIncomingDomainMoveV1 Rate-limited

domains_acceptIncomingDomainMoveV1 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": {
    "domains_acceptIncomingDomainMoveV1": {
      "limits": [
        {
          "counter": "domains_acceptincomingdomainmovev1_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 Hostinger Api, apply this rule, and every domains_acceptIncomingDomainMoveV1 call is checked against it from then on.

FAQ

Questions about domains_acceptIncomingDomainMoveV1

What does the domains_acceptIncomingDomainMoveV1 tool do? +

Accept an incoming move for a specified domain. The provided WHOIS profiles become the contacts of the domain, so they must belong to your account and satisfy the requirements of the TLD. Only the contact types the domain actually uses are applied, but all four profile IDs have to be provided. The move has to still be waiting for your decision, already accepted moves cannot be accepted again. Accepting does not complete the move. A confirmation email is sent to the email address of the new owner contact, and the domain changes hands only after the change is confirmed from it. Until then the move stays in the activating status, which can be followed with the [incoming move endpoint](#tag/domains-move). Use this endpoint to take ownership of a domain offered to you. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does domains_acceptIncomingDomainMoveV1 accept? +

domains_acceptIncomingDomainMoveV1 accepts 2 parameters: domain, domain_contacts. Required: domain, domain_contacts. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domains_acceptIncomingDomainMoveV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for domains_acceptIncomingDomainMoveV1: 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 Hostinger Api. Nothing to install.

What risk level is domains_acceptIncomingDomainMoveV1? +

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

Can I rate-limit domains_acceptIncomingDomainMoveV1? +

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

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

domains_acceptIncomingDomainMoveV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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