sendVerifyIdentityWithId

Send a verification code using the appropriate transport for the identity type being verified.

SERVERFusionauth SOURCE@fusionauth/mcp-api
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.)

Questions about sendVerifyIdentityWithId

What does the sendVerifyIdentityWithId tool do? +

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.

How do I enforce a policy on sendVerifyIdentityWithId? +

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.

What risk level is sendVerifyIdentityWithId? +

sendVerifyIdentityWithId is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sendVerifyIdentityWithId? +

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.

How do I block sendVerifyIdentityWithId completely? +

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.

What MCP server provides sendVerifyIdentityWithId? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fusionauth's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.