Delete a WordPress category
AI agents call delete_category to permanently remove resources in WordPressMCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of categories is an irreversible action that destroys data structure and content organization. While not as critical as user deletion, it has significant blast radius: categories organize content, and deleting one breaks taxonomies and potentially affects site navigation and content discoverability. This is more severe than Write operations but less critical than Financial actions.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a WordPress category' — this irreversibly removes a taxonomy term and will orphan or recategorize associated posts, causing permanent data loss.
Attacks that exploit this kind of access
Delete a WordPress category. It is categorised as a Destructive tool in the WordPressMCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WordPressMCP 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 WordPressMCP 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 WordPressMCP Server MCP server (jahzlariosa/wordpress-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 →