updateUserActionWithId
Updates the user action with the given Id. OR Reactivates the user action with the given Id.
This record as markdown: /tools/io-fusionauth-mcp-api/updateuseractionwithid.md
What updateUserActionWithId does on Fusionauth
AI agents use updateUserActionWithId 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 updateUserActionWithId is rated Medium
This tool modifies user action state (updates or reactivates), which is a Write operation. High severity is warranted because user actions may control authentication, access control, or security postures that could affect multiple user accounts or system behavior when modified. The operation is reversible (updates/reactivation vs. deletion), so it is Write rather than Destructive.
From the tool's definition 'Updates the user action with the given Id' indicates modification of existing data. 'Reactivates the user action' suggests state changes to user actions that are reversible operations.
Attacks that exploit this kind of access
The rule that runs updateUserActionWithId 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 updateUserActionWithId, this is the rule to start with:
updateUserActionWithId 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 updateUserActionWithId call is checked against it from then on.
Questions about updateUserActionWithId
Updates the user action with the given Id. OR Reactivates the user action with the given Id. 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 updateUserActionWithId: 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.
updateUserActionWithId 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 updateUserActionWithId 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 updateUserActionWithId. 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.
updateUserActionWithId 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