Gets a list of build definitions (pipeline configurations) in a project
AI agents call pipelines_get_build_definitions to retrieve information from Azure DevOps Multi-Organization MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists pipeline definitions without triggering builds, modifying configurations, or executing any external operations. It is a pure read operation with no side effects. The low severity reflects that exposure of pipeline configuration metadata poses minimal risk compared to tools that execute, modify, or delete resources.
From the tool's definition Tool name contains 'get' and description states 'Gets a list of build definitions (pipeline configurations)' — a query operation that retrieves existing pipeline configurations without modification or execution.
Attacks that exploit this kind of access
Gets a list of build definitions (pipeline configurations) in a project. It is categorised as a Read tool in the Azure DevOps Multi-Organization MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps Multi-Organization MCP Server MCP server in PolicyLayer and add a rule for pipelines_get_build_definitions: 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 Multi-Organization MCP Server. Nothing to install.
pipelines_get_build_definitions 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 pipelines_get_build_definitions 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 pipelines_get_build_definitions. 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.
pipelines_get_build_definitions is provided by the Azure DevOps Multi-Organization MCP Server MCP server (nikydobrev/mcp-server-azure-devops-multi). 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 →