domains_changeWHOISProfileForDomainV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-changewhoisprofilefordomainv1.md

WHAT IT DOES

What domains_changeWHOISProfileForDomainV1 does on Hostinger Api

AI agents use domains_changeWHOISProfileForDomainV1 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
`change_for`	array	Yes	Contact roles to repoint to the new WHOIS profile
`new_whois_id`	integer	Yes	WHOIS profile ID to assign to the domain

Parameters from the server's own tool schema.

RISK

Why domains_changeWHOISProfileForDomainV1 is rated Medium

This tool modifies domain registration contact information (WHOIS) and submits changes to the registry. It is a Write operation as it updates existing data, but carries high severity because altering domain ownership/contact info can affect domain control, trigger IRTP verification processes, and has regulatory implications. It is reversible in principle but has significant real-world consequences if misused.

From the tool's definition Change WHOIS contact profile for a domain... Repoints the given contact roles to a new WHOIS profile and submits the change to the registry.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domains_changeWHOISProfileForDomainV1 Rate-limited

domains_changeWHOISProfileForDomainV1 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_changeWHOISProfileForDomainV1": {
      "limits": [
        {
          "counter": "domains_changewhoisprofilefordomainv1_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_changeWHOISProfileForDomainV1 call is checked against it from then on.

FAQ

Questions about domains_changeWHOISProfileForDomainV1

What does the domains_changeWHOISProfileForDomainV1 tool do? +

Change WHOIS contact profile for a domain. Repoints the given contact roles to a new WHOIS profile and submits the change to the registry. The profile currently assigned to those roles is resolved automatically; the request fails if the given roles are not all on the same profile today. Changing transfer sensitive fields on the owner contact starts an IRTP verification. The change is processed asynchronously. Use this endpoint to move a registered domain onto different contact information. 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_changeWHOISProfileForDomainV1 accept? +

domains_changeWHOISProfileForDomainV1 accepts 3 parameters: domain, change_for, new_whois_id. Required: domain, change_for, new_whois_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domains_changeWHOISProfileForDomainV1? +

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

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

Can I rate-limit domains_changeWHOISProfileForDomainV1? +

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

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

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