domains_getDomainAuthorizationCodeV1
Retrieve the authorization (EPP) code for a specified domain so it can be transferred away from Hostinger to another registrar. Requesting a new code invalidates any code retrieved previously. Use this endpoint to obtain the code required to transfer a domain to another registrar.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-getdomainauthorizationcodev1.md
What domains_getDomainAuthorizationCodeV1 does on Hostinger Api
AI agents call domains_getDomainAuthorizationCodeV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
Parameters from the server's own tool schema.
Why domains_getDomainAuthorizationCodeV1 is rated Low
Even though domains_getDomainAuthorizationCodeV1 only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs domains_getDomainAuthorizationCodeV1 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_getDomainAuthorizationCodeV1, this is the rule to start with:
domains_getDomainAuthorizationCodeV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every domains_getDomainAuthorizationCodeV1 call is checked against it from then on.
Questions about domains_getDomainAuthorizationCodeV1
Retrieve the authorization (EPP) code for a specified domain so it can be transferred away from Hostinger to another registrar. Requesting a new code invalidates any code retrieved previously. Use this endpoint to obtain the code required to transfer a domain to another registrar. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
domains_getDomainAuthorizationCodeV1 accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for domains_getDomainAuthorizationCodeV1: 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.
domains_getDomainAuthorizationCodeV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the domains_getDomainAuthorizationCodeV1 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.
Set action: deny in the PolicyLayer policy for domains_getDomainAuthorizationCodeV1. 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.
domains_getDomainAuthorizationCodeV1 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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue