sendVerifyIdentityWithId
Send a verification code using the appropriate transport for the identity type being verified.
This record as markdown: /tools/io-fusionauth-mcp-api/sendverifyidentitywithid.md
What sendVerifyIdentityWithId does on Fusionauth
AI agents invoke sendVerifyIdentityWithId 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 sendVerifyIdentityWithId is rated High
This tool sends a verification code to a user via an external transport (email, SMS, etc.). It triggers an external side-effecting operation rather than simply reading or writing data in FusionAuth. It is not destructive or financial, but it does cause real-world effects (message delivery) that depend on the arguments provided, placing it in the Execute category.
From the tool's definition 'Send a verification code using the appropriate transport' — triggers an external operation (sending a message via email/SMS/etc.)
Attacks that exploit this kind of access
The rule that runs sendVerifyIdentityWithId 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 sendVerifyIdentityWithId, this is the rule to start with:
sendVerifyIdentityWithId 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 sendVerifyIdentityWithId call is checked against it from then on.
Questions about sendVerifyIdentityWithId
Send a verification code using the appropriate transport for the identity type being verified. 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 sendVerifyIdentityWithId: 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.
sendVerifyIdentityWithId 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 sendVerifyIdentityWithId 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 sendVerifyIdentityWithId. 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.
sendVerifyIdentityWithId 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