generateTwoFactorRecoveryCodesWithId
Generate two-factor recovery codes for a user. Generating two-factor recovery codes will invalidate any existing recovery codes.
This record as markdown: /tools/io-fusionauth-mcp-api/generatetwofactorrecoverycodeswithid.md
What generateTwoFactorRecoveryCodesWithId does on Fusionauth
AI agents use generateTwoFactorRecoveryCodesWithId 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 generateTwoFactorRecoveryCodesWithId is rated Medium
This tool creates new security credentials (recovery codes) and invalidates existing ones. While it modifies user data, it is reversible (new codes can be generated again if needed), making it Write rather than Destructive. The high severity reflects that misuse could lock a user out of their account or compromise their 2FA security by forcing generation of codes that only the attacker knows.
From the tool's definition Tool description states "Generating two-factor recovery codes will invalidate any existing recovery codes." This modifies user security credentials by replacing old codes with new ones.
Attacks that exploit this kind of access
The rule that runs generateTwoFactorRecoveryCodesWithId 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 generateTwoFactorRecoveryCodesWithId, this is the rule to start with:
generateTwoFactorRecoveryCodesWithId 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 generateTwoFactorRecoveryCodesWithId call is checked against it from then on.
Questions about generateTwoFactorRecoveryCodesWithId
Generate two-factor recovery codes for a user. Generating two-factor recovery codes will invalidate any existing recovery codes. 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 generateTwoFactorRecoveryCodesWithId: 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.
generateTwoFactorRecoveryCodesWithId 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 generateTwoFactorRecoveryCodesWithId 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 generateTwoFactorRecoveryCodesWithId. 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.
generateTwoFactorRecoveryCodesWithId 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