This record as markdown: /tools/hostinger-mcp/ecommerce-stores-delete.md
What ecommerce_stores_delete does on Hostinger
AI agents call ecommerce_stores_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 ecommerce_stores_delete is rated Critical
This tool permanently removes an ecommerce store, which cannot be undone. The action destroys data and business-critical infrastructure. While not financial in itself, the loss of a store could have severe business consequences. This is clearly Destructive rather than Write (reversible modification) or Execute (effect-dependent).
From the tool's definition Tool name: ecommerce_stores_delete; description: 'Delete an ecommerce store.' The verb 'delete' combined with the scope of a complete ecommerce store indicates irreversible removal of data and configuration.
Attacks that exploit this kind of access
The rule that runs ecommerce_stores_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 ecommerce_stores_delete, this is the rule to start with:
ecommerce_stores_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 ecommerce_stores_delete call is checked against it from then on.
Questions about ecommerce_stores_delete
Delete an ecommerce store. 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 ecommerce_stores_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.
ecommerce_stores_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 ecommerce_stores_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 ecommerce_stores_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.
ecommerce_stores_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