List DevOps pipeline configurations registered in ServiceNow
AI agents call list_devops_pipelines to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of DevOps pipeline metadata stored in ServiceNow. It retrieves information about registered pipelines but does not execute, modify, or delete any data. The 'list' verb and the passive construction 'registered in ServiceNow' confirm no side effects occur.
From the tool's definition The tool name 'list_devops_pipelines' and description 'List DevOps pipeline configurations registered in ServiceNow' indicate a retrieval operation that queries and returns existing pipeline configurations without modification or execution.
Attacks that exploit this kind of access
List DevOps pipeline configurations registered in ServiceNow. 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_devops_pipelines: 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_devops_pipelines 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_devops_pipelines 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_devops_pipelines. 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_devops_pipelines 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.
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 →