list_update_set_changes
A read tool on the ServiceNow MCP server.
This record as markdown: /tools/io-github-jschuller-mcp-server-servicenow/list-update-set-changes.md
What list_update_set_changes does on ServiceNow MCP Server
AI agents call list_update_set_changes 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 list_update_set_changes is rated Low
The 'list' operation pattern consistently denotes data retrieval. Even without an explicit description, 'list_update_set_changes' most naturally reads a collection of changes rather than modifying or deleting them. Sibling tools like 'create_update_set' and 'delete_record' demonstrate that the server supports write and destructive operations, making the absence of such verbs in this tool name significant.
From the tool's definition Tool name 'list_update_set_changes' uses the verb 'list', which retrieves or queries data. The description is empty, but the name and context (ServiceNow update sets) indicate it retrieves a list of changes within an update set—a read-only operation with no…
Attacks that exploit this kind of access
The rule that runs list_update_set_changes 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 list_update_set_changes, this is the rule to start with:
list_update_set_changes 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 list_update_set_changes call is checked against it from then on.
Questions about list_update_set_changes
list_update_set_changes is a read tool on the ServiceNow MCP Server MCP server. 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 list_update_set_changes: 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.
list_update_set_changes 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_update_set_changes 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_update_set_changes. 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_update_set_changes is provided by the ServiceNow MCP Server MCP server (pypi:mcp-server-servicenow). 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