This record as markdown: /tools/hostinger-mcp/hosting-db-delete.md
What hosting_db_delete does on Hostinger
AI agents call hosting_db_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_db_delete is rated Critical
Deletion of databases is an irreversible operation that cannot be undone and results in permanent loss of data. This is the most severe category (Destructive > Execute > Write > Read). High confidence due to unambiguous language in both name and description. Critical severity due to the potential for massive data loss and business disruption if an AI agent misuses this tool.
From the tool's definition Tool name 'hosting_db_delete' combined with description 'Delete a database' explicitly indicates irreversible deletion of data. The word 'delete' is a key destructive verb, and databases typically contain significant volumes of application data.
Attacks that exploit this kind of access
The rule that runs hosting_db_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_db_delete, this is the rule to start with:
hosting_db_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_db_delete call is checked against it from then on.
Questions about hosting_db_delete
Delete a database. 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_db_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_db_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_db_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_db_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_db_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