admin_delete_user
Löscht einen WordPress-Benutzer (erfordert Reassign)
This record as markdown: /tools/c-sakel-wp-mcp-server/admin-delete-user.md
What admin_delete_user does on WordPress MCP Server
AI agents call admin_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.
Why admin_delete_user is rated Critical
This tool permanently deletes WordPress user accounts, which is an irreversible action that cannot be undone. User deletion constitutes data destruction meeting the Destructive category. Severity is high rather than critical because it affects individual user accounts rather than system-wide infrastructure, though the impact could be significant depending on user role and associated content.
From the tool's definition Tool name 'admin_delete_user' combined with description 'Löscht einen WordPress-Benutzer' (German: 'Deletes a WordPress user') indicates irreversible deletion of user data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_delete_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_delete_user, this is the rule to start with:
admin_delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every admin_delete_user call is checked against it from then on.
Questions about admin_delete_user
Löscht einen WordPress-Benutzer (erfordert Reassign). 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 admin_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.
admin_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 admin_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 admin_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.
admin_delete_user is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
Across the catalogue