createUserVerifyEmail

Administratively verify a user

SERVERFusionauth SOURCE@fusionauth/mcp-api

Medium RISK CLASS

Category Write

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/createuserverifyemail.md

WHAT IT DOES

What createUserVerifyEmail does on Fusionauth

AI agents use createUserVerifyEmail 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.

RISK

Why createUserVerifyEmail is rated Medium

This tool modifies user account state by marking a user as email-verified, which is a reversible administrative action. It does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute).

From the tool's definition Tool name 'createUserVerifyEmail' and description 'Administratively verify a user' indicate modification of user state. The term 'verify' applied to a user account constitutes a change to user account status/attributes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs createUserVerifyEmail 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 createUserVerifyEmail, this is the rule to start with:

createUserVerifyEmail Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createUserVerifyEmail": {
      "limits": [
        {
          "counter": "createuserverifyemail_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fusionauth, apply this rule, and every createUserVerifyEmail call is checked against it from then on.

FAQ

Questions about createUserVerifyEmail

What does the createUserVerifyEmail tool do? +

Administratively verify a user. 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.

How do I enforce a policy on createUserVerifyEmail? +

Register the Fusionauth MCP server in PolicyLayer and add a rule for createUserVerifyEmail: 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 createUserVerifyEmail? +

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

Can I rate-limit createUserVerifyEmail? +

Yes. Add a rate_limit block to the createUserVerifyEmail 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 createUserVerifyEmail completely? +

Set action: deny in the PolicyLayer policy for createUserVerifyEmail. 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 createUserVerifyEmail? +

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

KEEP EXPLORING

More on Fusionauth, and thousands of servers like it.

This server

All 314 Fusionauth tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →