list_change_requests
List change requests with optional filtering by state or query
This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-change-requests.md
What list_change_requests does on ServiceNow-MCP
AI agents call list_change_requests to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_change_requests is rated Low
This tool retrieves or queries existing change request data from ServiceNow without creating, modifying, or deleting records. The optional filtering parameters allow querying by state or search criteria, but these are standard read-only filter operations. No side effects are produced. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't access, but cannot alter system state.
From the tool's definition Tool name 'list_change_requests' and description 'List change requests with optional filtering by state or query' indicate data retrieval with no modification or deletion. The verb 'list' and the filtering-only capability are characteristic of read operations.
Attacks that exploit this kind of access
The rule that runs list_change_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_change_requests, this is the rule to start with:
list_change_requests 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, apply this rule, and every list_change_requests call is checked against it from then on.
Questions about list_change_requests
List change requests with optional filtering by state or query. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP server in PolicyLayer and add a rule for list_change_requests: 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. Nothing to install.
list_change_requests 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 list_change_requests 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 list_change_requests. 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.
list_change_requests is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue