AI agents call get_pipeline to retrieve information from Ado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' naming convention combined with the server's core function of querying and analyzing Azure DevOps resources indicates this retrieves pipeline information without modification. The presence of separate create/delete tools confirms this is read-only. Tool description is empty, which slightly reduces confidence, but the context strongly supports a Read classification.
From the tool's definition Tool name 'get_pipeline' with siblings including 'create_pipeline', 'delete_pipeline', and 'analyze_pipeline_input' suggests a retrieval operation. The 'get_' prefix conventionally indicates a read-only query without side effects.
Attacks that exploit this kind of access
get_pipeline. It is categorised as a Read tool in the Ado MCP Server, which means it retrieves data without modifying state.
Register the Ado MCP server in PolicyLayer and add a rule for get_pipeline: 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 Ado. Nothing to install.
get_pipeline 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 get_pipeline 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 get_pipeline. 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.
get_pipeline is provided by the Ado MCP server (raboley/ado-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_pipeline is one line of Ado's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →