ecommerce_deleteStoreV1
Soft-delete a store owned by your account. The underlying store data is preserved; only the store is marked as deleted.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-deletestorev1.md
What ecommerce_deleteStoreV1 does on Hostinger Api
AI agents call ecommerce_deleteStoreV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
store_id | string | Yes | The ID of the store to delete. |
Parameters from the server's own tool schema.
Why ecommerce_deleteStoreV1 is rated Critical
This tool falls into the Destructive category because it removes a store from service, which is an irreversible action from the user's perspective. While the underlying data is preserved (soft-delete rather than hard-delete), the store itself is marked as deleted and taken offline, representing a significant and non-trivial action to undo.
From the tool's definition Tool performs a deletion operation: 'Soft-delete a store owned by your account.' Even though it is characterized as a 'soft-delete' with data preservation, it irreversibly removes the store from operational access and cannot be easily undone by an AI agent…
Attacks that exploit this kind of access
The rule that runs ecommerce_deleteStoreV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ecommerce_deleteStoreV1, this is the rule to start with:
ecommerce_deleteStoreV1 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 Api, apply this rule, and every ecommerce_deleteStoreV1 call is checked against it from then on.
Questions about ecommerce_deleteStoreV1
Soft-delete a store owned by your account. The underlying store data is preserved; only the store is marked as deleted. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
ecommerce_deleteStoreV1 accepts 1 parameter: store_id. Required: store_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for ecommerce_deleteStoreV1: 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 Api. Nothing to install.
ecommerce_deleteStoreV1 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_deleteStoreV1 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_deleteStoreV1. 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_deleteStoreV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue