domains_claimFreeDomainTransferV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 42 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-claimfreedomaintransferv1.md

WHAT IT DOES

What domains_claimFreeDomainTransferV1 does on Hostinger Api

AI agents use domains_claimFreeDomainTransferV1 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
`auth_code`	string	Yes	Authorization code from the current registrar
`should_keep_ns`	boolean	—	Keep the existing nameservers of the domain
`domain_contacts`	object	—	Domain contact information

Parameters from the server's own tool schema.

RISK

Why domains_claimFreeDomainTransferV1 is rated Medium

Initiates a domain transfer consuming a free transfer credit; significant but reversible account action.

From the tool's definition Claim a free domain transfer and start the transfer

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domains_claimFreeDomainTransferV1 Rate-limited

domains_claimFreeDomainTransferV1 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_claimFreeDomainTransferV1": {
      "limits": [
        {
          "counter": "domains_claimfreedomaintransferv1_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_claimFreeDomainTransferV1 call is checked against it from then on.

FAQ

Questions about domains_claimFreeDomainTransferV1

What does the domains_claimFreeDomainTransferV1 tool do? +

Claim a free domain transfer available on your account and start the transfer. Unlike purchasing a transfer, this consumes a free domain transfer you already have, so no payment method is required. Before making request, unlock the domain at the current registrar and get its authorization code. The transfer is validated first, so domains which cannot be transferred are rejected before the free domain transfer is consumed. A successful response means the transfer has been started. Completion depends on the current registrar and can be followed with the [transfer list endpoint](#tag/domains-transfer). If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Requests which cannot be fulfilled are rejected with an error code in the response body. Use this endpoint to transfer a domain using a free domain transfer from your account. 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_claimFreeDomainTransferV1 accept? +

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

How do I enforce a policy on domains_claimFreeDomainTransferV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for domains_claimFreeDomainTransferV1: 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_claimFreeDomainTransferV1? +

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

Can I rate-limit domains_claimFreeDomainTransferV1? +

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

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

domains_claimFreeDomainTransferV1 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 →