wp_delete_user

Delete a user permanently, reassigning their content to another user

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

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/io-github-cvrt-jh-wordpress-mcp/wp-delete-user.md

WHAT IT DOES

What wp_delete_user does on Wordpress

AI agents call wp_delete_user to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why wp_delete_user is rated Critical

Permanently deletes user accounts, irreversible action with significant consequences.

From the tool's definition Delete a user permanently, reassigning their content

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_delete_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_delete_user, this is the rule to start with:

wp_delete_user Hidden

wp_delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "wp_delete_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every wp_delete_user call is checked against it from then on.

FAQ

Questions about wp_delete_user

What does the wp_delete_user tool do? +

Delete a user permanently, reassigning their content to another user. It is categorised as a Destructive tool in the Wordpress 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 wp_delete_user? +

Register the Wordpress MCP server in PolicyLayer and add a rule for wp_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. Nothing to install.

What risk level is wp_delete_user? +

wp_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 wp_delete_user? +

Yes. Add a rate_limit block to the wp_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 wp_delete_user completely? +

Set action: deny in the PolicyLayer policy for wp_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 wp_delete_user? +

wp_delete_user is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →