wordpress_delete_category
AI agents call wordpress_delete_category to permanently remove resources in WordPress MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of WordPress categories is an irreversible action that removes data and can affect site organization, taxonomy structure, and potentially associated posts. This falls squarely into the Destructive category (irreversibly deletes data) rather than Write (reversible changes).
From the tool's definition Tool name 'wordpress_delete_category' contains 'delete', which indicates irreversible removal of data. The empty description provides no mitigating details, but the action clearly aligns with destructive operations that cannot be undone.
Attacks that exploit this kind of access
wordpress_delete_category. It is categorised as a Destructive tool in the WordPress MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_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 MCP Server. Nothing to install.
wordpress_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 wordpress_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 wordpress_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.
wordpress_delete_category is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/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 →