update_user · WordPressMCP Server MCP: Risk & Policy

WHAT IT DOES

What update_user does on WordPressMCP Server

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

WHY IT NEEDS A POLICY

Why update_user needs a policy

The tool modifies user data (profiles, roles, permissions, contact info) but does not irreversibly delete it. While user account modifications can have significant side effects (e.g., changing admin status), the operation is reversible through subsequent updates. This qualifies as Write rather than Execute or Destructive.

From the tool's definition Tool name is 'update_user' and description states 'Update a WordPress user', indicating modification of existing user data. This is a write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_user Rate-limited

update_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": {
    "update_user": {
      "limits": [
        {
          "counter": "update_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 WordPressMCP Server, so you can run agents against it safely.

FAQ

Questions about update_user

What does the update_user tool do? +

Update a WordPress user. It is categorised as a Write tool in the WordPressMCP 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 update_user? +

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

What risk level is update_user? +

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

Can I rate-limit update_user? +

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

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

update_user is provided by the WordPressMCP Server MCP server (jahzlariosa/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.