woo_delete_category
Delete a product category
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/woo-delete-category.md
What woo_delete_category does on Wordpress
AI agents call woo_delete_category to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why woo_delete_category is rated Critical
Deleting a product category is a destructive action that cannot be automatically undone. While the severity is not critical (unless the category contains many products with critical dependencies), the irreversible nature of the deletion and potential data loss classify this as Destructive rather than Write.
From the tool's definition Tool name 'woo_delete_category' and description 'Delete a product category' directly indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs woo_delete_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For woo_delete_category, this is the rule to start with:
woo_delete_category 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 Wordpress, apply this rule, and every woo_delete_category call is checked against it from then on.
Questions about woo_delete_category
Delete a product category. It is categorised as a Destructive tool in the Wordpress MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wordpress MCP server in PolicyLayer and add a rule for woo_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 Wordpress. Nothing to install.
woo_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 woo_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 woo_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.
woo_delete_category is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
Across the catalogue