AI agents call delete-category to permanently remove resources in AutoWP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a WordPress category is an irreversible action that removes taxonomy structure from the site. While not as severe as deleting all posts, it destroys category data and associations that cannot be automatically recovered. This warrants high severity due to potential site structural damage and loss of organizational metadata. Confidence is high because the action is unambiguously destructive.
From the tool's definition Tool name 'delete-category' combined with description 'Delete a WordPress category' indicates irreversible deletion of data. The verb 'delete' directly maps to the Destructive category definition.
Documented attack patterns abuse exactly the kind of access delete-category gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-category:
{
"version": "1",
"default": "deny",
"hide": [
"delete-category"
]
}delete-category disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a WordPress category. It is categorised as a Destructive tool in the AutoWP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AutoWP MCP 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 AutoWP MCP 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 AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.