retrieveUser

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 call retrieveUser to retrieve information from Mcp Api without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON RETRIEVEUSER

Even though retrieveUser only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-fusionauth-mcp-api.yaml

tools:
  retrieveUser:
    rules:
      - action: allow

See the full Mcp Api policy for all 310 tools.

// DETAILS

Tool Name retrieveUser

Category Read

MCP Server Mcp Api MCP Server

Risk Level Low

// 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 retrieveUser tool do? +

Retrieves the user for the given Id. This method does not use an API key, instead it uses a JSON Web Token (JWT) for authentication. OR Retrieves the user by a verificationId. The intended use of this API is to retrieve a user after the forgot password workflow has been initiated and you may not know the user's email or username. OR Retrieves the user for the given username. OR Retrieves the user for the loginId, using specific loginIdTypes. OR Retrieves the user for the loginId. The loginId can be either the username or the email. OR Retrieves the user for the given email. OR Retrieves the user by a change password Id. The intended use of this API is to retrieve a user after the forgot password workflow has been initiated and you may not know the user's email or username.. It is categorised as a Read tool in the Mcp Api MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieveUser? +

Add a rule in your Intercept YAML policy under the tools section for retrieveUser. 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 retrieveUser? +

retrieveUser is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit retrieveUser? +

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

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

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

retrieveUser

Enforce policies on Mcp Api