find-user

Finds users by filtering with name, email, or other criteria

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/find-user.md

WHAT IT DOES

What find-user does on Mcp Dev

AI agents call find-user to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find-user is rated Low

The find-user tool retrieves user information based on search criteria. It performs a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. While it accesses user data which could be considered sensitive, the tool itself is purely informational and non-destructive.

From the tool's definition Tool description states it 'Finds users by filtering with name, email, or other criteria' — this is a search/query operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find-user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find-user, this is the rule to start with:

find-user Allowed

find-user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find-user": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every find-user call is checked against it from then on.

FAQ

Questions about find-user

What does the find-user tool do? +

Finds users by filtering with name, email, or other criteria. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find-user? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for find-user: 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 Mcp Dev. Nothing to install.

What risk level is find-user? +

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

Can I rate-limit find-user? +

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

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

find-user is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 419 Mcp Dev tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →