admin_delete_user

Löscht einen WordPress-Benutzer (erfordert Reassign)

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about admin_delete_user

What does the admin_delete_user tool do? +

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.

How do I enforce a policy on admin_delete_user? +

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.

What risk level is admin_delete_user? +

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.

Can I rate-limit admin_delete_user? +

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.

How do I block admin_delete_user completely? +

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.

What MCP server provides admin_delete_user? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of WordPress MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.