Get a ServiceNow user by username, email, or sys_id. Args: - identifier (string): Username (jdoe), email (jdoe@company.com), or sys_id - response_format: Output format Returns: Full user record including sys_id, name, email, department, manager, roles Examples: - Get by username → identifier=
AI agents call servicenow_get_user to retrieve information from Servicenow 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 from ServiceNow without creating, modifying, or deleting any data. It is a straightforward read operation that queries existing records and returns results. The blast radius of misuse is minimal—at worst, it exposes user directory information that is typically accessible within an organization's ServiceNow instance.
From the tool's definition Tool description states 'Get a ServiceNow user by username, email, or sys_id' and 'Returns: Full user record' with no modification or side effects. The verb 'Get' and return-only operation clearly indicate data retrieval.
Attacks that exploit this kind of access
Get a ServiceNow user by username, email, or sys_id. Args: - identifier (string): Username (jdoe), email (jdoe@company.com), or sys_id - response_format: Output format Returns: Full user record including sys_id, name, email, department, manager, roles Examples: - Get by username → identifier=. It is categorised as a Read tool in the Servicenow MCP Server, which means it retrieves data without modifying state.
Register the Servicenow MCP server in PolicyLayer and add a rule for servicenow_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. Nothing to install.
servicenow_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 servicenow_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 servicenow_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.
servicenow_get_user is provided by the Servicenow MCP server (kylburns89/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 →