domains_unsetDefaultWHOISProfileV1

Unset WHOIS contact profile as default. The profile itself is kept, it is only no longer pre-selected for its TLD. Use this endpoint to stop reusing contact information for new registrations.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 11 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-unsetdefaultwhoisprofilev1.md

WHAT IT DOES

What domains_unsetDefaultWHOISProfileV1 does on Hostinger Api

AI agents use domains_unsetDefaultWHOISProfileV1 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
`whoisId`	integer	Yes	WHOIS ID

Parameters from the server's own tool schema.

RISK

Why domains_unsetDefaultWHOISProfileV1 is rated Medium

This tool modifies a configuration setting (removes the default flag from a WHOIS profile) but does not delete any data. The profile remains intact; only its default status changes. This is a reversible write operation with low blast radius since it only affects which profile is pre-selected for new domain registrations.

From the tool's definition Unset WHOIS contact profile as default. The profile itself is kept, it is only no longer pre-selected for its TLD.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domains_unsetDefaultWHOISProfileV1 Rate-limited

domains_unsetDefaultWHOISProfileV1 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_unsetDefaultWHOISProfileV1": {
      "limits": [
        {
          "counter": "domains_unsetdefaultwhoisprofilev1_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_unsetDefaultWHOISProfileV1 call is checked against it from then on.

FAQ

Questions about domains_unsetDefaultWHOISProfileV1

What does the domains_unsetDefaultWHOISProfileV1 tool do? +

Unset WHOIS contact profile as default. The profile itself is kept, it is only no longer pre-selected for its TLD. Use this endpoint to stop reusing contact information for new registrations. 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_unsetDefaultWHOISProfileV1 accept? +

domains_unsetDefaultWHOISProfileV1 accepts 1 parameter: whoisId. Required: whoisId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domains_unsetDefaultWHOISProfileV1? +

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

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

Can I rate-limit domains_unsetDefaultWHOISProfileV1? +

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

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

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