Medium Risk

update_pull_request

Update an existing pull request

How to control update_pull_request ↓

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

Medium Risk

Updating a pull request is a reversible modification operation. It changes PR properties but does not execute code, delete data, or move money. The severity is medium because a misused update could alter PR review status or assignments affecting CI/CD workflows, but changes are auditable and reversible.

From the tool's definition Tool name is 'update_pull_request' and description states 'Update an existing pull request' — this modifies an existing resource (pull request metadata, description, reviewers, etc.) reversibly without deleting data.

Documented attack patterns abuse exactly the kind of access update_pull_request gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for update_pull_request:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_pull_request": {
      "limits": [
        {
          "counter": "update_pull_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Azure DevOps MCP Server for Cline — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the update_pull_request tool do? +

Update an existing pull request. It is categorised as a Write tool in the Azure DevOps MCP Server for Cline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_pull_request? +

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

What risk level is update_pull_request? +

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

Can I rate-limit update_pull_request? +

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

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

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

Enforce policy on every Azure DevOps MCP Server for Cline tool call.

Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.