AI agents call extract_pipeline_run_data 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 uses 'extract' and 'data', which are read-oriented operations. Sibling tools like 'analyze_pipeline_input' confirm the server is used for querying/analyzing Azure DevOps data. No evidence of modification, deletion, code execution, or financial operations.
From the tool's definition Tool name 'extract_pipeline_run_data' indicates data retrieval/extraction without modification. No description provided, but context from sibling tools (analyze_pipeline_input, extract_pipeline_run_data_by_name) and server purpose (view logs, analyze…
Attacks that exploit this kind of access
extract_pipeline_run_data. 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 extract_pipeline_run_data: 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.
extract_pipeline_run_data 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 extract_pipeline_run_data 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 extract_pipeline_run_data. 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.
extract_pipeline_run_data 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.
extract_pipeline_run_data 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 →