domains_disable_privacy

Disable WHOIS privacy protection.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/domains-disable-privacy.md

WHAT IT DOES

What domains_disable_privacy does on Hostinger

AI agents use domains_disable_privacy to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.

RISK

Why domains_disable_privacy is rated Medium

This tool changes domain configuration state by disabling privacy protection, which is a reversible modification (privacy can be re-enabled). It does not delete data or execute arbitrary code, placing it in the Write category.

From the tool's definition 'Disable WHOIS privacy protection' - modifies domain privacy settings by removing an active protection mechanism

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs domains_disable_privacy safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains_disable_privacy, this is the rule to start with:

domains_disable_privacy Rate-limited

domains_disable_privacy 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_disable_privacy": {
      "limits": [
        {
          "counter": "domains_disable_privacy_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, apply this rule, and every domains_disable_privacy call is checked against it from then on.

FAQ

Questions about domains_disable_privacy

What does the domains_disable_privacy tool do? +

Disable WHOIS privacy protection. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on domains_disable_privacy? +

Register the Hostinger MCP server in PolicyLayer and add a rule for domains_disable_privacy: 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. Nothing to install.

What risk level is domains_disable_privacy? +

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

Can I rate-limit domains_disable_privacy? +

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

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

domains_disable_privacy is provided by the Hostinger MCP server (idugeni/hostinger-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, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →