wordpress_delete_user
AI agents call wordpress_delete_user 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.
User deletion is irreversible and cannot be undone without restoration from backups. The blast radius is critical: deleting users removes access, may cascade to delete user-generated content (posts, comments), loses authentication credentials, and disrupts site management. This is a Destructive action rather than merely Write. The empty description lowers confidence only slightly, as the function name is unambiguous.
From the tool's definition Tool name is 'wordpress_delete_user' which explicitly indicates irreversible deletion of user accounts. No description provided, but the name alone clearly indicates a destructive action on user data.
Attacks that exploit this kind of access
wordpress_delete_user. 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_user: 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_user 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_user 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_user. 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_user 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.
wordpress_delete_user is one line of WordPress MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →