Delete a WordPress tag
AI agents call delete_tag 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.
The delete_tag tool irreversibly removes a tag from a WordPress site. While the blast radius is somewhat contained—a tag deletion affects taxonomy metadata rather than core content—it is permanent and cannot be undone through the tool itself. An AI agent misusing this could remove important organizational structures. This is classified as Destructive rather than Write because deletion is irreversible.
From the tool's definition Tool name: 'delete_tag'. Description: 'Delete a WordPress tag'. The verb 'Delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a WordPress tag. 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_tag: 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_tag 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_tag 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_tag. 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_tag 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 →