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

hosting_parked_delete

Remove a parked domain.

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-parked-delete.md

What hosting_parked_delete does on Hostinger

AI agents call hosting_parked_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_parked_delete is rated Critical

This tool permanently deletes a parked domain configuration, which cannot be undone without restoration from backups or re-creation. Domain removal is an irreversible operation that affects service availability and DNS routing. Classified as Destructive (rather than Execute) because the action is fundamentally about deletion, not conditional execution.

From the tool's definition Tool name 'hosting_parked_delete' combined with description 'Remove a parked domain' explicitly indicates deletion of a domain configuration. The verb 'delete' and 'remove' are irreversible actions.

Questions about hosting_parked_delete

What does the hosting_parked_delete tool do? +

Remove a parked domain. 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_parked_delete? +

Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_parked_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_parked_delete? +

hosting_parked_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_parked_delete? +

Yes. Add a rate_limit block to the hosting_parked_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_parked_delete completely? +

Set action: deny in the PolicyLayer policy for hosting_parked_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_parked_delete? +

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