This record as markdown: /tools/hostinger-mcp/domains-delete-whois-profile.md
What domains_delete_whois_profile does on Hostinger
AI agents call domains_delete_whois_profile to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why domains_delete_whois_profile is rated Critical
The tool performs an irreversible deletion operation on WHOIS profile data. While not catastrophic at the infrastructure level, deleting WHOIS profiles cannot be undone and may impact domain privacy settings or administrative contact information. This qualifies as Destructive rather than Write because deletion is not reversible.
From the tool's definition Tool name contains 'delete' and description states 'Delete a WHOIS profile' — this irreversibly removes WHOIS profile data.
Attacks that exploit this kind of access
The rule that runs domains_delete_whois_profile 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_delete_whois_profile, this is the rule to start with:
domains_delete_whois_profile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every domains_delete_whois_profile call is checked against it from then on.
Questions about domains_delete_whois_profile
Delete a WHOIS profile. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for domains_delete_whois_profile: 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.
domains_delete_whois_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the domains_delete_whois_profile 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_delete_whois_profile. 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_delete_whois_profile 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.
More on Hostinger, and thousands of servers like it.
Across the catalogue