List all pipelines in a project
AI agents call list_project_pipelines to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about pipelines without side effects. It falls clearly into the Read category as it only fetches data about existing pipelines. The severity is low because listing pipelines exposes informational metadata about project infrastructure but does not permit execution, modification, or deletion of those pipelines.
From the tool's definition The tool name and description indicate a retrieval operation: 'list_project_pipelines' performs a list action to retrieve pipelines from a project with no modification, creation, deletion, or execution of those pipelines.
Attacks that exploit this kind of access
List all pipelines in a project. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for list_project_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 Azure DevOps MCP Server. Nothing to install.
list_project_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_project_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_project_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_project_pipelines is provided by the Azure DevOps MCP Server MCP server (jaybird-us/azure-devops-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 →