get_user
Look up user details by email or username
This record as markdown: /tools/servicenow-mcp-server/get-user.md
What get_user does on ServiceNow MCP Server
AI agents call get_user to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_user is rated Low
This tool performs a read-only query to fetch user details. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. The blast radius of misuse is limited to information disclosure of user details, which is a low severity concern. The clear intent to retrieve rather than transform data places it squarely in the Read category.
From the tool's definition Tool name 'get_user' and description 'Look up user details by email or username' indicate a query/lookup operation that retrieves user information without modifying or executing operations.
Attacks that exploit this kind of access
The rule that runs get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user, this is the rule to start with:
get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every get_user call is checked against it from then on.
Questions about get_user
Look up user details by email or username. 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 get_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 ServiceNow MCP Server. Nothing to install.
get_user 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_user is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue