startVerifyIdentityWithId
Start a verification of an identity by generating a code. This code can be sent to the User using the Verify Send API Verification Code API or using a mechanism outside of FusionAuth. The verification is completed by using the Verify Complete API with this code.
This record as markdown: /tools/io-fusionauth-mcp-api/startverifyidentitywithid.md
What startVerifyIdentityWithId does on Fusionauth
AI agents invoke startVerifyIdentityWithId 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 startVerifyIdentityWithId is rated High
This tool triggers a security-critical operation (identity verification) that generates codes and initiates verification workflows. While not destructive or financial, it executes a significant business operation with side effects—it commits FusionAuth to tracking a verification state that affects user authentication flows. Misuse could enable unauthorized identity verification attempts or flooding attacks.
From the tool's definition The tool description states it will 'generate a code' and 'start a verification of an identity', which are operations that trigger external state changes in the FusionAuth system.
Attacks that exploit this kind of access
The rule that runs startVerifyIdentityWithId 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 startVerifyIdentityWithId, this is the rule to start with:
startVerifyIdentityWithId 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 startVerifyIdentityWithId call is checked against it from then on.
Questions about startVerifyIdentityWithId
Start a verification of an identity by generating a code. This code can be sent to the User using the Verify Send API Verification Code API or using a mechanism outside of FusionAuth. The verification is completed by using the Verify Complete API with this code. 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 startVerifyIdentityWithId: 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.
startVerifyIdentityWithId 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 startVerifyIdentityWithId 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 startVerifyIdentityWithId. 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.
startVerifyIdentityWithId 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