delete_product_category

Delete one or more product categories by id.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/delete-product-category.md

What delete_product_category does on Webcake Storefront

AI agents call delete_product_category to permanently remove resources in Webcake Storefront, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_product_category is rated Critical

This tool permanently removes product categories from the storefront, which cannot be undone. Deletion of categories could cascade to affect product organization, customer navigation, and sales operations. While not financial in nature, the destructive capacity makes this high severity—an AI agent misusing this could corrupt the store's product taxonomy.

From the tool's definition Tool name is 'delete_product_category' and description states 'Delete one or more product categories by id.' The verb 'delete' combined with the capability to remove one or more categories indicates irreversible data destruction.

Questions about delete_product_category

What does the delete_product_category tool do? +

Delete one or more product categories by id. It is categorised as a Destructive tool in the Webcake Storefront MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_product_category? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for delete_product_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 Webcake Storefront. Nothing to install.

What risk level is delete_product_category? +

delete_product_category is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_product_category? +

Yes. Add a rate_limit block to the delete_product_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.

How do I block delete_product_category completely? +

Set action: deny in the PolicyLayer policy for delete_product_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.

What MCP server provides delete_product_category? +

delete_product_category is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Webcake Storefront, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Webcake Storefront's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.