deleteUserActionReasonWithId

Deletes the user action reason for the given Id.

SERVERFusionauth SOURCE@fusionauth/mcp-api
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What deleteUserActionReasonWithId does on Fusionauth

AI agents call deleteUserActionReasonWithId to permanently remove resources in Fusionauth, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why deleteUserActionReasonWithId is rated Critical

This tool performs an irreversible deletion operation on user action reason data. Deletion operations that cannot be undone fall into the Destructive category. The severity is high because unintended deletion of user action reasons could impact audit trails, compliance records, or the ability to track user actions—potentially affecting multiple users or system integrity depending on how FusionAuth uses this data.

From the tool's definition Tool name contains 'delete' and description states 'Deletes the user action reason for the given Id.' The verb 'Deletes' indicates irreversible removal of data.

Questions about deleteUserActionReasonWithId

What does the deleteUserActionReasonWithId tool do? +

Deletes the user action reason for the given Id. It is categorised as a Destructive tool in the Fusionauth MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deleteUserActionReasonWithId? +

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

deleteUserActionReasonWithId is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteUserActionReasonWithId? +

Yes. Add a rate_limit block to the deleteUserActionReasonWithId 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 deleteUserActionReasonWithId completely? +

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

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

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