AI agents call delete_category to permanently remove resources in PrestaShop MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible delete operation on a data entity (category). This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because category deletion in a live e-commerce store could break product organization, customer navigation, and SEO structures, with potential business impact.
From the tool's definition Tool name 'delete_category' and description 'Delete a category' indicate irreversible deletion of data. Categories in e-commerce systems typically contain references to products, customer navigation paths, and potentially orders; deletion cannot be undone…
Documented attack patterns abuse exactly the kind of access delete_category gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PrestaShop MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_category:
{
"version": "1",
"default": "deny",
"hide": [
"delete_category"
]
}delete_category disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a category. It is categorised as a Destructive tool in the PrestaShop MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PrestaShop MCP Server MCP server in PolicyLayer and add a rule for delete_category: 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 PrestaShop MCP Server. Nothing to install.
delete_category 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 delete_category 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 delete_category. 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.
delete_category is provided by the PrestaShop MCP Server MCP server (latinogino/prestashop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PrestaShop MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 PrestaShop MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.