generateTwoFactorSecretUsingJWTWithId
Generate a Two Factor secret that can be used to enable Two Factor authentication for a User. The response will contain both the secret and a Base32 encoded form of the secret which can be shown to a User when using a 2 Step Authentication application such as Google Authenticator.
This record as markdown: /tools/io-fusionauth-mcp-api/generatetwofactorsecretusingjwtwithid.md
What generateTwoFactorSecretUsingJWTWithId does on Fusionauth
AI agents use generateTwoFactorSecretUsingJWTWithId 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 generateTwoFactorSecretUsingJWTWithId is rated Medium
This tool creates or generates new authentication material (a 2FA secret) that modifies a user's security configuration. While it generates data rather than destructively removing it, and doesn't execute arbitrary code or move funds, the creation of authentication secrets is a write operation that increases the security posture of an account.
From the tool's definition The tool description states it will 'Generate a Two Factor secret' and 'can be used to enable Two Factor authentication for a User.' This involves creating and modifying authentication credentials for a user account, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs generateTwoFactorSecretUsingJWTWithId 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 generateTwoFactorSecretUsingJWTWithId, this is the rule to start with:
generateTwoFactorSecretUsingJWTWithId 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 generateTwoFactorSecretUsingJWTWithId call is checked against it from then on.
Questions about generateTwoFactorSecretUsingJWTWithId
Generate a Two Factor secret that can be used to enable Two Factor authentication for a User. The response will contain both the secret and a Base32 encoded form of the secret which can be shown to a User when using a 2 Step Authentication application such as Google Authenticator. 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 generateTwoFactorSecretUsingJWTWithId: 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.
generateTwoFactorSecretUsingJWTWithId 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 generateTwoFactorSecretUsingJWTWithId 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 generateTwoFactorSecretUsingJWTWithId. 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.
generateTwoFactorSecretUsingJWTWithId 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