Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations
AI agents call get_pull_request_changes to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and displays information about pull request changes without altering any data or triggering external operations. It is a retrieval/query operation typical of Read category tools. The blast radius of misuse is minimal—an agent could only view PR information it may not have intended to access, not modify or delete anything.
From the tool's definition The tool retrieves file changes and unified diffs in a pull request ('Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations').
Documented attack patterns abuse exactly the kind of access get_pull_request_changes 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 get_pull_request_changes:
{
"version": "1",
"default": "deny",
"tools": {
"get_pull_request_changes": {}
}
}get_pull_request_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for get_pull_request_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 Azure DevOps MCP Server. Nothing to install.
get_pull_request_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 get_pull_request_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 get_pull_request_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.
get_pull_request_changes 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.