Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags
AI agents use update_pull_request 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.
The tool modifies existing data (PR properties, reviewer assignments, work item links, tags) in a way that can be undone or changed again. This qualifies as Write rather than Execute (no code execution or external operations triggered), Destructive (reversible), or Read (has side effects).
From the tool's definition Tool description states 'Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags' — these are reversible modifications (updates, additions, removals) to PR metadata and associations, not deletions or…
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, and nothing reaches the server without passing your rules. This is the rule we recommend for update_pull_request:
{
"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.
Free to start. No card required.
Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags. 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.
Register the Azure DevOps MCP Server 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. Nothing to install.
update_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_pull_request is provided by the Azure DevOps MCP Server MCP server (tiberriver256/mcp-server-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.