claudeus_wp_users__update_user
Update an existing WordPress user. Modify user details, roles, or profile information.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-users--update-user.md
What claudeus_wp_users__update_user does on Claudeus WordPress MCP
AI agents use claudeus_wp_users__update_user to create or update resources in Claudeus WordPress MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudeus WordPress MCP environment.
Why claudeus_wp_users__update_user is rated Medium
This tool creates or modifies data reversibly by updating user accounts and their roles. While not destructive (changes can be undone), modifying user roles is high-severity because it can elevate privileges, lock out administrators, or compromise site security. Classified as Write rather than Execute because it modifies a data entity rather than running arbitrary commands.
From the tool's definition Tool name contains 'update_user' and description states 'Update an existing WordPress user. Modify user details, roles, or profile information.' This directly modifies user data including roles, which affects site permissions and access control.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_users__update_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_users__update_user, this is the rule to start with:
claudeus_wp_users__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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_users__update_user call is checked against it from then on.
Questions about claudeus_wp_users__update_user
Update an existing WordPress user. Modify user details, roles, or profile information. It is categorised as a Write tool in the Claudeus WordPress MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_users__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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_users__update_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the claudeus_wp_users__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.
Set action: deny in the PolicyLayer policy for claudeus_wp_users__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.
claudeus_wp_users__update_user is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
This server
Across the catalogue