Delete a category (DELETE /admin/api/ecommerce/v1/categories/
AI agents call category_delete to permanently remove resources in Voog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a category from the Voog CMS ecommerce system. Category deletion cannot be undone and affects the product taxonomy and potentially associated products. The DELETE HTTP method and explicit 'delete' semantics confirm destructive intent. This is more severe than Write (which is reversible) and reaches the Destructive category.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a category' with HTTP method 'DELETE', indicating irreversible removal of data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Delete a category (DELETE /admin/api/ecommerce/v1/categories/. It is categorised as a Destructive tool in the Voog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Voog MCP server in PolicyLayer and add a rule for category_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 Voog. Nothing to install.
category_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 category_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 category_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.
category_delete is provided by the Voog MCP server (runnel/voog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →