list_pull_requests
A read tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/list-pull-requests.md
What list_pull_requests does on Azure DevOps MCP Server
AI agents call list_pull_requests to retrieve information from Azure DevOps MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_pull_requests is rated Low
Listing pull requests is a read-only operation that retrieves and displays existing data without modifying, executing, or deleting anything. It carries minimal risk as the worst misuse would be information disclosure of PRs already accessible to the authenticated user.
From the tool's definition Tool name 'list_pull_requests' indicates a retrieval operation. Server description confirms the tool lists PRs as a non-destructive query. No description provided for the specific tool, but the name is clear.
Attacks that exploit this kind of access
The rule that runs list_pull_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Azure DevOps MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_pull_requests, this is the rule to start with:
list_pull_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Azure DevOps MCP Server, apply this rule, and every list_pull_requests call is checked against it from then on.
Questions about list_pull_requests
list_pull_requests is a read tool on the Azure DevOps MCP Server MCP server. 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 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 Azure DevOps MCP Server. 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 Azure DevOps MCP Server MCP server (abdelrhmansror/azuredevopsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Azure DevOps MCP Server, and thousands of servers like it.
This server
Across the catalogue