This record as markdown: /tools/io-fusionauth-mcp-api/createuserchangepassword.md
What createUserChangePassword does on Fusionauth
AI agents use createUserChangePassword to create or update resources in Fusionauth, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusionauth environment.
Why createUserChangePassword is rated Medium
This tool modifies user account state (password change) which is a reversible write operation. It affects user authentication credentials, making it high severity due to security implications, but it is Write rather than Execute/Destructive because the operation is a standard account management function.
From the tool's definition Tool name 'createUserChangePassword' and description 'Changes a user' indicate modification of user data. Related sibling tools like 'changePasswordWithId' confirm this server deals with user account modifications.
Attacks that exploit this kind of access
The rule that runs createUserChangePassword safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createUserChangePassword, this is the rule to start with:
createUserChangePassword 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 Fusionauth, apply this rule, and every createUserChangePassword call is checked against it from then on.
Questions about createUserChangePassword
Changes a user. It is categorised as a Write tool in the Fusionauth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusionauth MCP server in PolicyLayer and add a rule for createUserChangePassword: 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 Fusionauth. Nothing to install.
createUserChangePassword 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 createUserChangePassword 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 createUserChangePassword. 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.
createUserChangePassword is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
This server
Across the catalogue