createMessengerWithId
Creates a messenger. You can optionally specify an Id for the messenger, if not provided one will be generated.
This record as markdown: /tools/io-fusionauth-mcp-api/createmessengerwithid.md
What createMessengerWithId does on Fusionauth
AI agents use createMessengerWithId 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 createMessengerWithId is rated Medium
This tool creates a new messenger resource in FusionAuth, which is a reversible write operation. The severity is medium because creating unauthorized messengers could enable unintended communication channels or credential exposure, but the impact is limited to messenger configuration rather than financial or security-critical systems. High confidence due to clear 'create' semantics in name and description.
From the tool's definition Tool name includes 'create' and description states 'Creates a messenger', which is a data creation operation with optional ID specification.
Attacks that exploit this kind of access
The rule that runs createMessengerWithId 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 createMessengerWithId, this is the rule to start with:
createMessengerWithId 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 createMessengerWithId call is checked against it from then on.
Questions about createMessengerWithId
Creates a messenger. You can optionally specify an Id for the messenger, if not provided one will be generated. 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 createMessengerWithId: 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.
createMessengerWithId 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 createMessengerWithId 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 createMessengerWithId. 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.
createMessengerWithId 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