completeVerifyIdentityWithId
Completes verification of an identity using verification codes from the Verify Start API.
This record as markdown: /tools/io-fusionauth-mcp-api/completeverifyidentitywithid.md
What completeVerifyIdentityWithId does on Fusionauth
AI agents use completeVerifyIdentityWithId 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 completeVerifyIdentityWithId is rated Medium
This tool modifies user identity verification status reversibly—a critical authentication/identity state change. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). The high severity reflects the security-sensitive nature of identity verification state in an auth system: misuse could unlock unauthorized account access or bypass verification requirements.
From the tool's definition Tool description states it 'Completes verification of an identity using verification codes', indicating it modifies identity verification state.
Attacks that exploit this kind of access
The rule that runs completeVerifyIdentityWithId 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 completeVerifyIdentityWithId, this is the rule to start with:
completeVerifyIdentityWithId 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 completeVerifyIdentityWithId call is checked against it from then on.
Questions about completeVerifyIdentityWithId
Completes verification of an identity using verification codes from the Verify Start API. 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 completeVerifyIdentityWithId: 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.
completeVerifyIdentityWithId 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 completeVerifyIdentityWithId 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 completeVerifyIdentityWithId. 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.
completeVerifyIdentityWithId 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