AI agents use set_user_password to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.
This tool modifies user account state (password) but the change is reversible—another password can be set later. It is not a destructive deletion. However, it carries high severity because unauthorized password changes could lock legitimate users out of their accounts or enable account takeover, especially on an autonomous infrastructure platform serving paid coding agents.
From the tool's definition Tool name 'set_user_password' and description 'Change, reset, or set a user' indicate modification of user account credentials.
Attacks that exploit this kind of access
Change, reset, or set a user. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Run402 MCP server in PolicyLayer and add a rule for set_user_password: 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 Run402. Nothing to install.
set_user_password 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 set_user_password 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 set_user_password. 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.
set_user_password is provided by the Run402 MCP server (kychee-com/run402). 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 →