domains_deleteWHOISProfileV1
Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-deletewhoisprofilev1.md
What domains_deleteWHOISProfileV1 does on Hostinger Api
AI agents call domains_deleteWHOISProfileV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
whoisId | integer | Yes | WHOIS ID |
Parameters from the server's own tool schema.
Why domains_deleteWHOISProfileV1 is rated Critical
The tool performs an irreversible deletion operation on WHOIS contact profile data. Once deleted, the profile cannot be recovered through normal means. This is a destructive operation that modifies account configuration and cannot be undone, making it more severe than a Write operation. While not directly financial, unauthorized deletion could disrupt domain management operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete WHOIS contact profile' and 'remove unused contact profiles from account'. This irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs domains_deleteWHOISProfileV1 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_deleteWHOISProfileV1, this is the rule to start with:
domains_deleteWHOISProfileV1 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 Api, apply this rule, and every domains_deleteWHOISProfileV1 call is checked against it from then on.
Questions about domains_deleteWHOISProfileV1
Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
domains_deleteWHOISProfileV1 accepts 1 parameter: whoisId. Required: whoisId. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for domains_deleteWHOISProfileV1: 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.
domains_deleteWHOISProfileV1 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_deleteWHOISProfileV1 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_deleteWHOISProfileV1. 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_deleteWHOISProfileV1 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.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue