Get a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scoped)
AI agents call get_pull_request 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 retrieves pull request information by ID. The verb 'Get' and the lack of any modification language (create, update, delete) clearly indicate a read-only operation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an attacker could only learn about pull request contents that exist, which does not compromise system integrity or cause destructive effects.
From the tool's definition Tool name is 'get_pull_request' and description states 'Get a pull request by ID', indicating retrieval of existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_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 get_pull_request:
{
"version": "1",
"default": "deny",
"tools": {
"get_pull_request": {}
}
}get_pull_request 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 a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scoped). 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: 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 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 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. 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 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.