wordpress_create_user · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_create_user does on WordPress MCP Server

AI agents use wordpress_create_user to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.

WHY IT NEEDS A POLICY

Why wordpress_create_user needs a policy

Creating user accounts is a Write operation that modifies system state reversibly (users can be deleted). While reversible, creating users has high severity because it grants access to the WordPress system and could escalate privileges if combined with sibling tools like 'wordpress_add_capability' and 'wordpress_assign_role', creating unauthorized administrative accounts.

From the tool's definition Tool name indicates user creation functionality ('wordpress_create_user'); empty description limits specificity but context shows server manages complete WordPress control including user management capabilities (see sibling tools like 'wordpress_assign_role').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_create_user Rate-limited

wordpress_create_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_create_user": {
      "limits": [
        {
          "counter": "wordpress_create_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_create_user

What does the wordpress_create_user tool do? +

wordpress_create_user. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wordpress_create_user? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_create_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 wordpress_create_user? +

wordpress_create_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wordpress_create_user? +

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

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

wordpress_create_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.