startTwoFactorLoginWithId
Start a Two-Factor login request by generating a two-factor identifier. This code can then be sent to the Two Factor Send API (/api/two-factor/send)in order to send a one-time use code to a user. You can also use one-time use code returned to send the code out-of-band. The Two-Factor login is com...
This record as markdown: /tools/io-fusionauth-mcp-api/starttwofactorloginwithid.md
What startTwoFactorLoginWithId does on Fusionauth
AI agents invoke startTwoFactorLoginWithId 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 startTwoFactorLoginWithId is rated High
This tool initiates a two-factor authentication flow for a user account identified by 'WithId', which is an executable operation that triggers side effects in the authentication system. While it does not modify user data directly (Write) or delete anything (Destructive), it executes a complex authentication workflow with potential impact on account access.
From the tool's definition Tool description indicates it 'Start[s] a Two-Factor login request by generating a two-factor identifier' and is part of a login workflow that 'can then be sent to the Two Factor Send API' and 'completed by making a request to the Two-Factor Login API'.
Attacks that exploit this kind of access
The rule that runs startTwoFactorLoginWithId 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 startTwoFactorLoginWithId, this is the rule to start with:
startTwoFactorLoginWithId 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 startTwoFactorLoginWithId call is checked against it from then on.
Questions about startTwoFactorLoginWithId
Start a Two-Factor login request by generating a two-factor identifier. This code can then be sent to the Two Factor Send API (/api/two-factor/send)in order to send a one-time use code to a user. You can also use one-time use code returned to send the code out-of-band. The Two-Factor login is completed by making a request to the Two-Factor Login API (/api/two-factor/login). with the two-factor identifier and the one-time use code. This API is intended to allow you to begin a Two-Factor login outside a normal login that originated from the Login API (/api/login). 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 startTwoFactorLoginWithId: 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.
startTwoFactorLoginWithId 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 startTwoFactorLoginWithId 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 startTwoFactorLoginWithId. 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.
startTwoFactorLoginWithId 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