List service requests (sc_request) for current user or with filter
AI agents call requests_list 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 tool queries and retrieves service request records from ServiceNow, filtered optionally by user or other criteria. It performs no side effects, creates no data, executes no code, and deletes nothing. It is purely a read operation that falls squarely into the Read category with low severity since listing requests has minimal blast radius even if misused by an agent.
From the tool's definition Tool name 'requests_list' and description 'List service requests (sc_request) for current user or with filter' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List service requests (sc_request) for current user or with filter. 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 requests_list: 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.
requests_list 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 requests_list 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 requests_list. 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.
requests_list is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). 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 →