# domains_acceptIncomingDomainMoveV1 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. Agent View of the PolicyLayer registry record for `domains_acceptIncomingDomainMoveV1`. HTML page: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-acceptincomingdomainmovev1 ## Facts - Tool: `domains_acceptIncomingDomainMoveV1` - Server: Hostinger Api (`hostinger-api-mcp`) — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md - Install: `npx -y hostinger-api-mcp` - Homepage: https://github.com/hostinger/api-mcp-server - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 2 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | 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. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "domains_acceptIncomingDomainMoveV1", "arguments": { "domain": "", "domain_contacts": {} } } } ``` ## 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 own definition: "Tool performs 'Accept an incoming move for a specified domain' with requirement to provide contact profiles." ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hostinger Api: ```json { "version": "1", "default": "deny", "tools": { "domains_acceptIncomingDomainMoveV1": { "limits": [ { "counter": "domains_acceptincomingdomainmovev1_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Hostinger Api (381) - `agency-hosting_clearWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-clearwebsitecachev1.md - `agency-hosting_deleteWebsiteCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deletewebsitecronjobv1.md - `agency-hosting_deleteWebsiteDatabaseUserV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deletewebsitedatabaseuserv1.md - `agency-hosting_deleteWebsiteDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deletewebsitedatabasev1.md - `agency-hosting_deleteWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deletewebsitev1.md - `agency-hosting_deployNodeStaticWebsite` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deploynodestaticwebsite.md - `agency-hosting_deployPhpApplication` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deployphpapplication.md - `billing_deletePaymentMethodV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/billing-deletepaymentmethodv1.md - `DNS_deleteDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-deletednsrecordsv1.md - `DNS_resetDNSRecordsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/dns-resetdnsrecordsv1.md - `domains_cancelPendingIRTPVerificationV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-cancelpendingirtpverificationv1.md - `domains_deleteDomainForwardingV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletedomainforwardingv1.md - `domains_deleteWHOISProfileV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/domains-deletewhoisprofilev1.md - `ecommerce_cancelAnOrderV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-cancelanorderv1.md - `ecommerce_deleteAProductV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deleteaproductv1.md - `ecommerce_deleteAProductVariantV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deleteaproductvariantv1.md - `ecommerce_deleteStoreV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deletestorev1.md - `hosting_clearNode_jsRuntimeLogsV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-clearnode-jsruntimelogsv1.md - `hosting_clearWebsiteCacheV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-clearwebsitecachev1.md - `hosting_deleteAccountCronJobV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountcronjobv1.md - `hosting_deleteAccountDatabaseV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabasev1.md - `hosting_deleteDatabaseRemoteConnectionV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletedatabaseremoteconnectionv1.md - `hosting_deleteWebsiteParkedDomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsiteparkeddomainv1.md - `hosting_deleteWebsiteRedirectV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsiteredirectv1.md - `hosting_deleteWebsiteSubdomainV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitesubdomainv1.md - `hosting_deleteWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewebsitev1.md - `hosting_deleteWordPressInstallationV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deletewordpressinstallationv1.md - `hosting_deployStaticSiteArchiveV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-deploystaticsitearchivev1.md - `hosting_importWordPressWebsiteV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-importwordpresswebsitev1.md - `hosting_startNode_jsBuildV1` — Destructive — https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp/hosting-startnode-jsbuildv1.md - …and 351 more: https://policylayer.com/tools/io-github-hostinger-hostinger-api-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-hostinger-hostinger-api-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-hostinger-hostinger-api-mcp