loginWithId
Authenticates a user to FusionAuth. This API optionally requires an API key. See <code>Application.loginConfiguration.requireAuthentication</code>.
This record as markdown: /tools/io-fusionauth-mcp-api/loginwithid.md
What loginWithId does on Fusionauth
AI agents invoke loginWithId to trigger actions in Fusionauth. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why loginWithId is rated High
Authenticating a user is not a simple read or write; it executes an authentication flow that produces tokens, sessions, and audit events in FusionAuth. Misuse could allow an AI agent to authenticate as arbitrary users, potentially bypassing access controls. The optional API key requirement lowers the barrier for misuse in some configurations.
From the tool's definition 'Authenticates a user to FusionAuth' — triggers an external authentication operation with session/token side effects
Attacks that exploit this kind of access
The rule that runs loginWithId 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 loginWithId, this is the rule to start with:
loginWithId stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 loginWithId call is checked against it from then on.
Questions about loginWithId
Authenticates a user to FusionAuth. This API optionally requires an API key. See <code>Application.loginConfiguration.requireAuthentication</code>. It is categorised as a Execute tool in the Fusionauth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fusionauth MCP server in PolicyLayer and add a rule for loginWithId: 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.
loginWithId is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the loginWithId 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 loginWithId. 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.
loginWithId 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