sendTwoFactorCodeForEnableDisableWithId
Send a Two Factor authentication code to assist in setting up Two Factor authentication or disabling.
This record as markdown: /tools/io-fusionauth-mcp-api/sendtwofactorcodeforenabledisablewithid.md
What sendTwoFactorCodeForEnableDisableWithId does on Fusionauth
AI agents invoke sendTwoFactorCodeForEnableDisableWithId 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 sendTwoFactorCodeForEnableDisableWithId is rated High
This tool triggers an external operation — sending a 2FA code via email/SMS/etc. to a user. It's not purely a read or write operation; it actively dispatches a message through an external communication channel. Misuse could be used to harass users with repeated code sends or as part of a social engineering attack to disable 2FA.
From the tool's definition Send a Two Factor authentication code to assist in setting up Two Factor authentication or disabling
Attacks that exploit this kind of access
The rule that runs sendTwoFactorCodeForEnableDisableWithId 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 sendTwoFactorCodeForEnableDisableWithId, this is the rule to start with:
sendTwoFactorCodeForEnableDisableWithId 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 sendTwoFactorCodeForEnableDisableWithId call is checked against it from then on.
Questions about sendTwoFactorCodeForEnableDisableWithId
Send a Two Factor authentication code to assist in setting up Two Factor authentication or disabling. 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 sendTwoFactorCodeForEnableDisableWithId: 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.
sendTwoFactorCodeForEnableDisableWithId 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 sendTwoFactorCodeForEnableDisableWithId 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 sendTwoFactorCodeForEnableDisableWithId. 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.
sendTwoFactorCodeForEnableDisableWithId 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