createUserActionReasonWithId
Creates a user reason. This user action reason cannot be used when actioning a user until this call completes successfully. Anytime after that the user action reason can be used.
This record as markdown: /tools/io-fusionauth-mcp-api/createuseractionreasonwithid.md
What createUserActionReasonWithId does on Fusionauth
AI agents use createUserActionReasonWithId 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 createUserActionReasonWithId is rated Medium
This tool creates a new user action reason record in the FusionAuth system. The operation is reversible (the reason can be deleted or modified later) and has no side effects beyond adding a new record. It does not execute code, delete data irreversibly, or move funds.
From the tool's definition The tool description states 'Creates a user reason' and explicitly indicates it adds a new entity that 'can be used' afterward, indicating persistent data creation without deletion.
Attacks that exploit this kind of access
The rule that runs createUserActionReasonWithId 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 createUserActionReasonWithId, this is the rule to start with:
createUserActionReasonWithId 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 createUserActionReasonWithId call is checked against it from then on.
Questions about createUserActionReasonWithId
Creates a user reason. This user action reason cannot be used when actioning a user until this call completes successfully. Anytime after that the user action reason can be used. 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 createUserActionReasonWithId: 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.
createUserActionReasonWithId 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 createUserActionReasonWithId 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 createUserActionReasonWithId. 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.
createUserActionReasonWithId 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