activateReactorWithId
Activates the FusionAuth Reactor using a license Id and optionally a license text (for air-gapped deployments)
This record as markdown: /tools/io-fusionauth-mcp-api/activatereactorwithid.md
What activateReactorWithId does on Fusionauth
AI agents use activateReactorWithId 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 activateReactorWithId is rated Medium
This tool activates a reactor (a premium FusionAuth feature) by writing license configuration to the system. While not destructive (the action is theoretically reversible by deactivation), it creates a material change in system state and licensing posture. The high severity reflects that unauthorized reactor activation could enable unauthorized features or bypass licensing controls.
From the tool's definition Tool description states it 'Activates the FusionAuth Reactor using a license Id' — this modifies system configuration/licensing state. The presence of license parameters indicates data modification that activates a system component.
Attacks that exploit this kind of access
The rule that runs activateReactorWithId 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 activateReactorWithId, this is the rule to start with:
activateReactorWithId 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 activateReactorWithId call is checked against it from then on.
Questions about activateReactorWithId
Activates the FusionAuth Reactor using a license Id and optionally a license text (for air-gapped deployments). 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 activateReactorWithId: 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.
activateReactorWithId 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 activateReactorWithId 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 activateReactorWithId. 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.
activateReactorWithId 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