Update a user (email, name, password, groups, profile fields).
AI agents use wiki_user_update to create or update resources in Mcp Wikijs Mv — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wikijs Mv environment.
This tool modifies user data including sensitive attributes like passwords and group memberships, which could affect authentication and authorization. However, updates are reversible (passwords can be changed again, group assignments adjusted), distinguishing this from destructive deletion.
From the tool's definition Tool description states 'Update a user' with capabilities to modify email, name, password, groups, and profile fields. These are reversible modifications to user accounts.
Attacks that exploit this kind of access
Update a user (email, name, password, groups, profile fields). It is categorised as a Write tool in the Mcp Wikijs Mv MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_user_update: 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 Mcp Wikijs Mv. Nothing to install.
wiki_user_update 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 wiki_user_update 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 wiki_user_update. 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.
wiki_user_update is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →