AI agents use create_pipeline to create or update resources in Ado — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ado environment.
Creating a pipeline is a write operation that generates new CI/CD infrastructure and configuration in Azure DevOps. While reversible (pipelines can be deleted), it has significant blast radius: an AI could create malicious pipelines, trigger unintended builds, or consume resources.
From the tool's definition Tool named 'create_pipeline' with no description; however context shows this server enables 'run pipelines' and the sibling tools include 'delete_pipeline' and 'analyze_pipeline_input', confirming pipeline manipulation capabilities.
Attacks that exploit this kind of access
create_pipeline. It is categorised as a Write tool in the Ado MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ado MCP server in PolicyLayer and add a rule for create_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.
create_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
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 →