watch_pipeline_by_name · Ado MCP: Risk & Policy

WHAT IT DOES

What watch_pipeline_by_name does on Ado

AI agents invoke watch_pipeline_by_name to trigger actions in Ado. 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 watch_pipeline_by_name needs a policy

The description is empty, so classification relies on the tool name and server context. 'Watch' could mean monitoring (Read) or triggering and watching a pipeline run (Execute). Given the server explicitly supports running pipelines and sibling tools include 'create_pipeline' and 'extract_pipeline_run_data', 'watch_pipeline_by_name' most plausibly triggers and monitors a pipeline execution, which is Execute.

From the tool's definition Tool name 'watch_pipeline_by_name' and server description mentions 'run pipelines' — watching a pipeline may involve triggering/monitoring pipeline execution in Azure DevOps.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

watch_pipeline_by_name Rate-limited

watch_pipeline_by_name 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": {
    "watch_pipeline_by_name": {
      "limits": [
        {
          "counter": "watch_pipeline_by_name_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 Ado, so you can run agents against it safely.

FAQ

Questions about watch_pipeline_by_name

What does the watch_pipeline_by_name tool do? +

watch_pipeline_by_name. It is categorised as a Execute tool in the Ado MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on watch_pipeline_by_name? +

Register the Ado MCP server in PolicyLayer and add a rule for watch_pipeline_by_name: 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.

What risk level is watch_pipeline_by_name? +

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

Can I rate-limit watch_pipeline_by_name? +

Yes. Add a rate_limit block to the watch_pipeline_by_name 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 watch_pipeline_by_name completely? +

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

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