Search for users
AI agents call user_search to retrieve information from ServiceNow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward search/query operation with no side effects. It retrieves user records from ServiceNow but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an AI agent could potentially enumerate users or gather organizational information, but cannot cause harm through this tool alone. Classified as Read with low severity.
From the tool's definition Tool name 'user_search' and description 'Search for users' indicate a query operation that retrieves user information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Search for users. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for user_search: 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 ServiceNow MCP Server. Nothing to install.
user_search 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 user_search 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 user_search. 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.
user_search is provided by the ServiceNow MCP Server MCP server (lokimcpuniverse/servicenow-mcp-server). 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 →