Get pull request details
AI agents call get_pull_request to retrieve information from MCP Server for Azure DevOps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing pull request data without side effects. It falls squarely into the Read category as it fetches information without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could retrieve sensitive PR information but cannot alter repositories, trigger builds, or perform destructive actions.
From the tool's definition Tool name 'get_pull_request' and description 'Get pull request details' indicate a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get pull request details. It is categorised as a Read tool in the MCP Server for Azure DevOps MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Azure DevOps 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 MCP Server for Azure DevOps. 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 MCP Server for Azure DevOps MCP server (sepal7/mcp-ado). 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 →