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

agency_website_delete

Delete an Agency Plan website.

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/agency-website-delete.md

What agency_website_delete does on Hostinger

AI agents call agency_website_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 agency_website_delete is rated Critical

This tool permanently removes a website, which is an irreversible destructive action. The blast radius is high because deletion of a production website could disrupt business operations, cause data loss, and require significant recovery effort. While not financial in nature, it ranks as Destructive (more severe than Write or Execute) because the action cannot be reversed through normal tool operations.

From the tool's definition 'Delete an Agency Plan website' — the verb 'Delete' combined with the scope 'website' indicates irreversible removal of a resource. This cannot be undone without restoration from backups.

Questions about agency_website_delete

What does the agency_website_delete tool do? +

Delete an Agency Plan website. 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 agency_website_delete? +

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

agency_website_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 agency_website_delete? +

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

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

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