createUserAction
Creates a user action. This action cannot be taken on a user until this call successfully returns. Anytime after that the user action can be applied to any user.
This record as markdown: /tools/io-fusionauth-mcp-api/createuseraction.md
What createUserAction does on Fusionauth
AI agents use createUserAction 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 createUserAction is rated Medium
This tool creates a new user action record in the FusionAuth system. While this is a write operation (not read-only), it does not delete or overwrite data (not Destructive), does not execute arbitrary code (not Execute), and does not move financial resources (not Financial).
From the tool's definition The tool description states it "Creates a user action", which is a write operation that creates data. The description explicitly indicates this creates a new user action resource that persists and can be applied to users afterwards.
Attacks that exploit this kind of access
The rule that runs createUserAction 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 createUserAction, this is the rule to start with:
createUserAction 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 createUserAction call is checked against it from then on.
Questions about createUserAction
Creates a user action. This action cannot be taken on a user until this call successfully returns. Anytime after that the user action can be applied to any 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 createUserAction: 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.
createUserAction 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 createUserAction 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 createUserAction. 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.
createUserAction 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