ado_complete_pull_request · Mcp Azure MCP: Risk & Policy

WHAT IT DOES

What ado_complete_pull_request does on Mcp Azure

AI agents invoke ado_complete_pull_request to trigger actions in Mcp Azure. 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 ado_complete_pull_request needs a policy

Merging a pull request is an irreversible or hard-to-reverse operation that triggers external git operations (merging code into a branch), potentially affecting the main/production codebase. While not purely destructive (data isn't deleted), it executes a significant external operation with broad blast radius if misused by an AI agent.

From the tool's definition Completa (merge) un Pull Request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ado_complete_pull_request Rate-limited

ado_complete_pull_request 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": {
    "ado_complete_pull_request": {
      "limits": [
        {
          "counter": "ado_complete_pull_request_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 Mcp Azure, so you can run agents against it safely.

FAQ

Questions about ado_complete_pull_request

What does the ado_complete_pull_request tool do? +

Completa (merge) un Pull Request. It is categorised as a Execute tool in the Mcp Azure MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ado_complete_pull_request? +

Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_complete_pull_request: 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 Mcp Azure. Nothing to install.

What risk level is ado_complete_pull_request? +

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

Can I rate-limit ado_complete_pull_request? +

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

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

ado_complete_pull_request is provided by the Mcp Azure MCP server (soulberto/mcp-azure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.