AI agents use ado_add_pull_request_reviewer to create or update resources in Mcp Azure — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Azure environment.
This tool creates or modifies metadata on a pull request by adding a reviewer assignment. It is reversible (a reviewer can be removed), produces no side effects beyond updating PR state, and does not execute code, delete data, or move money. It fits the Write category as it modifies data reversibly.
From the tool's definition Tool name 'ado_add_pull_request_reviewer' and description 'Agrega un revisor a un Pull Request' (adds a reviewer to a pull request) indicate a modification operation that changes PR metadata by assigning a reviewer.
Attacks that exploit this kind of access
Agrega un revisor a un Pull Request. It is categorised as a Write tool in the Mcp Azure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_add_pull_request_reviewer: 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.
ado_add_pull_request_reviewer 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 ado_add_pull_request_reviewer 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 ado_add_pull_request_reviewer. 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.
ado_add_pull_request_reviewer 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →