updateUserVerifyEmail
Re-sends the verification email to the user. If the Application has configured a specific email template this will be used instead of the tenant configuration. OR Re-sends the verification email to the user. OR Generate a new Email Verification Id to be used with the Verify Email API. This API wi...
This record as markdown: /tools/io-fusionauth-mcp-api/updateuserverifyemail.md
What updateUserVerifyEmail does on Fusionauth
AI agents use updateUserVerifyEmail 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 updateUserVerifyEmail is rated Medium
The tool modifies user verification state by generating new verification IDs and triggering email sends. This is a write operation because it creates new verification records and initiates side effects (email delivery), but it is not destructive (reversible), not financial, and not arbitrary code execution.
From the tool's definition Tool performs 're-sends the verification email' and 'Generate a new Email Verification Id', which are state-modifying operations that create or update verification records and trigger email communications.
Attacks that exploit this kind of access
The rule that runs updateUserVerifyEmail 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 updateUserVerifyEmail, this is the rule to start with:
updateUserVerifyEmail 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 updateUserVerifyEmail call is checked against it from then on.
Questions about updateUserVerifyEmail
Re-sends the verification email to the user. If the Application has configured a specific email template this will be used instead of the tenant configuration. OR Re-sends the verification email to the user. OR Generate a new Email Verification Id to be used with the Verify Email API. This API will not attempt to send an email to the User. This API may be used to collect the verificationId for use with a third party system. 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 updateUserVerifyEmail: 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.
updateUserVerifyEmail 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 updateUserVerifyEmail 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 updateUserVerifyEmail. 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.
updateUserVerifyEmail 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