List pull requests in a repository
AI agents call list_pull_requests 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 lists pull requests, which is a read-only operation with no side effects. It does not create, modify, delete, execute code, or commit financial resources. The blast radius of misuse is minimal—an agent could potentially discover pull request information it shouldn't see, but cannot alter or delete anything.
From the tool's definition Tool name 'list_pull_requests' and description 'List pull requests in a repository' indicate a retrieval operation that queries existing data without modification.
Attacks that exploit this kind of access
List pull requests in a repository. 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 list_pull_requests: 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.
list_pull_requests 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 list_pull_requests 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 list_pull_requests. 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.
list_pull_requests 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 →