Search users by username, email, phone number or employee number.
AI agents call find_users to retrieve information from InvGate Service Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information without side effects. It performs a lookup operation across user attributes (username, email, phone, employee number) but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could enumerate users but cannot escalate privileges, modify data, or cause destructive effects through search alone.
From the tool's definition Tool name 'find_users' and description 'Search users by username, email, phone number or employee number' indicate a query/search operation with no modification of data.
Attacks that exploit this kind of access
Search users by username, email, phone number or employee number. It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for find_users: 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 InvGate Service Desk. Nothing to install.
find_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_users 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 find_users. 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.
find_users is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →