AI agents call get_pipeline_timeline 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 tool name strongly suggests a retrieval operation ('get_') that would fetch pipeline timeline/execution history data. Within the context of a DevOps server focused on viewing and analyzing pipelines, this fits the Read category (retrieves or queries data with no side effects). The absence of any action words like 'create', 'delete', 'run', or 'execute' supports this classification. Confidence is moderate-high (0.
From the tool's definition Tool name 'get_pipeline_timeline' and the server description indicating it enables viewing logs and analyzing failures suggests this retrieves pipeline execution timeline data without modifying it. The 'get_' prefix convention indicates a read operation.
Attacks that exploit this kind of access
get_pipeline_timeline. 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_timeline: 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_timeline 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_timeline 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_timeline. 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_timeline 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.
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 →