git.pr.update · Azure DevOps MCP Server MCP: Risk & Policy

WHAT IT DOES

What git.pr.update does on Azure DevOps MCP Server

AI agents use git.pr.update to create or update resources in Azure DevOps MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server environment.

WHY IT NEEDS A POLICY

Why git.pr.update needs a policy

This tool modifies the state of a Pull Request. While 'abandoned' could be considered somewhat destructive, PR status changes are generally reversible (an abandoned PR can be reactivated), making Write the most appropriate category.

From the tool's definition Updates a Pull Request status (active, abandoned, completed)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git.pr.update Rate-limited

git.pr.update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git.pr.update": {
      "limits": [
        {
          "counter": "git.pr.update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 MCP Server, so you can run agents against it safely.

FAQ

Questions about git.pr.update

What does the git.pr.update tool do? +

Updates a Pull Request status (active, abandoned, completed). It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git.pr.update? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for git.pr.update: 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 MCP Server. Nothing to install.

What risk level is git.pr.update? +

git.pr.update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git.pr.update? +

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

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

git.pr.update is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.