Fetches changes from an Azure DevOps Pull Request with full diff content using the Azure DevOps Node API.
AI agents call ado_pr_changes to retrieve information from Git Stuff Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays pull request changes and diff content without modifying any data. Fetching PR information is a read operation with no side effects or destructive capability. The low severity reflects that exposing PR diff data has minimal blast radius—it only reveals code changes that are typically already visible to authorized users in Azure DevOps.
From the tool's definition Tool description states it "Fetches changes from an Azure DevOps Pull Request with full diff content". The verb "Fetches" indicates data retrieval only. The parent server description emphasizes "generate diffs", further confirming read-only intent.
Attacks that exploit this kind of access
Fetches changes from an Azure DevOps Pull Request with full diff content using the Azure DevOps Node API. It is categorised as a Read tool in the Git Stuff Server MCP Server, which means it retrieves data without modifying state.
Register the Git Stuff Server MCP server in PolicyLayer and add a rule for ado_pr_changes: 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 Git Stuff Server. Nothing to install.
ado_pr_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ado_pr_changes 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_pr_changes. 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_pr_changes is provided by the Git Stuff Server MCP server (skurekjakub/gitstuffserver). 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 →