pipelines_run_pipeline

WHAT IT DOES

What pipelines_run_pipeline does on Azure DevOps Multi-Organization MCP Server

AI agents invoke pipelines_run_pipeline to trigger actions in Azure DevOps Multi-Organization MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why pipelines_run_pipeline needs a policy

This tool executes a CI/CD pipeline, which is an external operation whose consequences are not directly controlled by the tool itself but depend on what the pipeline does. While the direct action is triggering (not modifying pipeline definitions), the blast radius is high because pipelines commonly perform deployments, infrastructure changes, and other consequential operations.

From the tool's definition Tool name 'pipelines_run_pipeline' and description 'Triggers a new pipeline run' indicate execution of external operations (CI/CD pipeline execution).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pipelines_run_pipeline Rate-limited

pipelines_run_pipeline stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pipelines_run_pipeline": {
      "limits": [
        {
          "counter": "pipelines_run_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure DevOps Multi-Organization MCP Server, so you can run agents against it safely.

FAQ

Questions about pipelines_run_pipeline

What does the pipelines_run_pipeline tool do? +

Triggers a new pipeline run with optional parameters and variables. It is categorised as a Execute tool in the Azure DevOps Multi-Organization MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pipelines_run_pipeline? +

Register the Azure DevOps Multi-Organization MCP Server MCP server in PolicyLayer and add a rule for pipelines_run_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 Azure DevOps Multi-Organization MCP Server. Nothing to install.

What risk level is pipelines_run_pipeline? +

pipelines_run_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pipelines_run_pipeline? +

Yes. Add a rate_limit block to the pipelines_run_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.

How do I block pipelines_run_pipeline completely? +

Set action: deny in the PolicyLayer policy for pipelines_run_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.

What MCP server provides pipelines_run_pipeline? +

pipelines_run_pipeline 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.