list_update_sets

A read tool on the ServiceNow MCP server.

SERVERServiceNow MCP Server SOURCEpypi:mcp-server-servicenow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-jschuller-mcp-server-servicenow/list-update-sets.md

WHAT IT DOES

What list_update_sets does on ServiceNow MCP Server

AI agents call list_update_sets 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.

RISK

Why list_update_sets is rated Low

The 'list_' prefix is a standard pattern for retrieval operations that return collections without modification. Update sets in ServiceNow are configuration/code bundles; listing them has no side effects. Confidence is slightly reduced (0.85 vs 0.95) due to missing description, but the naming convention and sibling tool patterns (get_*, aggregate_*) strongly indicate Read category.

From the tool's definition Tool name 'list_update_sets' indicates retrieval/enumeration of update sets; no description provided, but 'list' pattern and context of sibling tools (aggregate_records, get_ci, get_record) confirm query-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_update_sets 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_sets, this is the rule to start with:

list_update_sets Allowed

list_update_sets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_update_sets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every list_update_sets call is checked against it from then on.

FAQ

Questions about list_update_sets

What does the list_update_sets tool do? +

list_update_sets 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.

How do I enforce a policy on list_update_sets? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for list_update_sets: 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.

What risk level is list_update_sets? +

list_update_sets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_update_sets? +

Yes. Add a rate_limit block to the list_update_sets 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.

How do I block list_update_sets completely? +

Set action: deny in the PolicyLayer policy for list_update_sets. 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.

What MCP server provides list_update_sets? +

list_update_sets 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.

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 19 ServiceNow MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →