patchUserActionReasonWithId

Updates, via PATCH, the user action reason with the given Id.

SERVERFusionauth SOURCE@fusionauth/mcp-api
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-fusionauth-mcp-api/patchuseractionreasonwithid.md

What patchUserActionReasonWithId does on Fusionauth

AI agents use patchUserActionReasonWithId 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 patchUserActionReasonWithId is rated Medium

This tool modifies existing data (user action reason) in a reversible manner. It is classified as Write rather than Read (no retrieval), Execute (no code execution or conditional side effects), Destructive (changes are reversible via another PATCH), or Financial.

From the tool's definition The tool description states it 'Updates, via PATCH, the user action reason with the given Id.' PATCH is an HTTP method for modifying existing data.

Questions about patchUserActionReasonWithId

What does the patchUserActionReasonWithId tool do? +

Updates, via PATCH, the user action reason 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.

How do I enforce a policy on patchUserActionReasonWithId? +

Register the Fusionauth MCP server in PolicyLayer and add a rule for patchUserActionReasonWithId: 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.

What risk level is patchUserActionReasonWithId? +

patchUserActionReasonWithId is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit patchUserActionReasonWithId? +

Yes. Add a rate_limit block to the patchUserActionReasonWithId 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.

How do I block patchUserActionReasonWithId completely? +

Set action: deny in the PolicyLayer policy for patchUserActionReasonWithId. 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.

What MCP server provides patchUserActionReasonWithId? +

patchUserActionReasonWithId 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fusionauth's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.