This record as markdown: /tools/hostinger-mcp/hosting-subdomains-delete.md
What hosting_subdomains_delete does on Hostinger
AI agents call hosting_subdomains_delete 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 hosting_subdomains_delete is rated Critical
Deletion of a subdomain cannot be undone and removes a live internet-facing resource. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' High severity because misconfiguration could break customer applications or DNS resolution. Confidence is high due to explicit 'delete' terminology in both name and description.
From the tool's definition Tool name contains 'delete' and description states 'Delete a subdomain' — this irreversibly removes a DNS/hosting resource.
Attacks that exploit this kind of access
The rule that runs hosting_subdomains_delete 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 hosting_subdomains_delete, this is the rule to start with:
hosting_subdomains_delete 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 hosting_subdomains_delete call is checked against it from then on.
Questions about hosting_subdomains_delete
Delete a subdomain. 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 hosting_subdomains_delete: 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.
hosting_subdomains_delete 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 hosting_subdomains_delete 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 hosting_subdomains_delete. 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.
hosting_subdomains_delete 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