Delete a tag in WordPress site.
AI agents call delete_tag 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 is an irreversible operation that permanently removes a tag and its associations from WordPress. This meets the Destructive category criterion: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is somewhat limited compared to deleting posts or users (tags are organizational metadata), the operation cannot be undone and could break content organization if…
From the tool's definition Tool name explicitly states 'delete_tag' with description 'Delete a tag in WordPress site.' The delete operation is irreversible and removes taxonomy data from the site.
Attacks that exploit this kind of access
Delete a tag in WordPress site. 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 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 WordPress MCP 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 WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). 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 →