New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

domains_delete_whois_profile

Delete a WHOIS profile.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about domains_delete_whois_profile

What does the domains_delete_whois_profile tool do? +

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.

How do I enforce a policy on domains_delete_whois_profile? +

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.

What risk level is domains_delete_whois_profile? +

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.

Can I rate-limit domains_delete_whois_profile? +

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.

How do I block domains_delete_whois_profile completely? +

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.

What MCP server provides domains_delete_whois_profile? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.