This record as markdown: /tools/stateset-mcp-server/stateset-change-password.md
What stateset_change_password does on Stateset
AI agents use stateset_change_password to create or update resources in Stateset, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stateset environment.
Why stateset_change_password is rated Medium
This tool modifies sensitive user authentication data (password), which is a Write operation that affects user account security. While reversible in principle (another password change), it represents a critical account security vector if misused by an AI agent.
From the tool's definition Tool name 'stateset_change_password' and description 'Changes a user' indicates modification of user account credentials.
Attacks that exploit this kind of access
The rule that runs stateset_change_password safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_change_password, this is the rule to start with:
stateset_change_password 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 Stateset, apply this rule, and every stateset_change_password call is checked against it from then on.
Questions about stateset_change_password
Changes a user\. It is categorised as a Write tool in the Stateset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_change_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 Stateset. Nothing to install.
stateset_change_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 stateset_change_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 stateset_change_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.
stateset_change_password is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
This server
Across the catalogue