Remove a category from the main navigation menu tree
AI agents call remove_category_from_menu 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.
Removing a category from the menu is an irreversible deletion of a navigation structure element. While the category itself may still exist, the menu entry is removed and this action is not automatically reversible without re-adding it manually. This qualifies as Destructive rather than Write because the operation deletes rather than modifies data.
From the tool's definition "Remove a category from the main navigation menu tree" — removes/deletes an item from the navigation menu
Documented attack patterns abuse exactly the kind of access remove_category_from_menu 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 remove_category_from_menu:
{
"version": "1",
"default": "deny",
"hide": [
"remove_category_from_menu"
]
} remove_category_from_menu 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.
Remove a category from the main navigation menu tree. 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 remove_category_from_menu: 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.
remove_category_from_menu 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 remove_category_from_menu 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 remove_category_from_menu. 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.
remove_category_from_menu 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.