updateUserVerifyEmail

Single-target operation

Part of the Mcp Api MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use updateUserVerifyEmail to create or modify resources in Mcp Api. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON UPDATEUSERVERIFYEMAIL

Without a policy, an AI agent could call updateUserVerifyEmail repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Api.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-fusionauth-mcp-api.yaml

tools:
  updateUserVerifyEmail:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Api policy for all 310 tools.

// DETAILS

Tool Name updateUserVerifyEmail

Category Write

MCP Server Mcp Api MCP Server

Risk Level Medium

// MORE MCP API TOOLS

Destructive cancelActionWithId Destructive changePasswordWithId Destructive deleteAPIKeyWithId Destructive deleteApplicationRoleWithId Destructive deleteApplicationWithId Destructive deleteConnectorWithId Destructive deleteConsentWithId Destructive deleteEmailTemplateWithId

View all 310 tools →

// RELATED READING

// FAQ

What does the updateUserVerifyEmail tool do? +

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 Mcp Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on updateUserVerifyEmail? +

Add a rule in your Intercept YAML policy under the tools section for updateUserVerifyEmail. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Api MCP server.

What risk level is updateUserVerifyEmail? +

updateUserVerifyEmail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit updateUserVerifyEmail? +

Yes. Add a rate_limit block to the updateUserVerifyEmail rule in your Intercept 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 updateUserVerifyEmail completely? +

Set action: deny in the Intercept 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.

What MCP server provides updateUserVerifyEmail? +

updateUserVerifyEmail is provided by the Mcp Api MCP server (@fusionauth/mcp-api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

updateUserVerifyEmail

Enforce policies on Mcp Api