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

hosting_subdomains_delete

Delete a subdomain.

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/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.

Questions about hosting_subdomains_delete

What does the hosting_subdomains_delete tool do? +

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.

How do I enforce a policy on hosting_subdomains_delete? +

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.

What risk level is hosting_subdomains_delete? +

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.

Can I rate-limit hosting_subdomains_delete? +

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.

How do I block hosting_subdomains_delete completely? +

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.

What MCP server provides hosting_subdomains_delete? +

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.

// 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.