list_deployment_history
List deployment history — committed update sets and app installs over time
This record as markdown: /tools/servicenow-mcp-server/list-deployment-history.md
What list_deployment_history does on ServiceNow MCP Server
AI agents call list_deployment_history 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_deployment_history is rated Low
This tool retrieves and displays deployment history records (update sets and app installs). It performs no data modification, deletion, or external execution. The verb 'list' and the read-only nature of accessing historical deployment data clearly place it in the Read category. Severity is low because querying historical metadata poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name 'list_deployment_history' with description 'List deployment history — committed update sets and app installs over time' indicates a retrieval/query operation that provides historical information without modification.
Attacks that exploit this kind of access
The rule that runs list_deployment_history 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_deployment_history, this is the rule to start with:
list_deployment_history 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_deployment_history call is checked against it from then on.
Questions about list_deployment_history
List deployment history — committed update sets and app installs over time. 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_deployment_history: 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_deployment_history 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_deployment_history 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_deployment_history. 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_deployment_history is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). 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