Low Risk

list_pull_requests

List all pull requests in the project

How to control list_pull_requests ↓

AI agents call list_pull_requests to retrieve information from Azure DevOps MCP Server for Cline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns pull request data without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation with minimal security risk, as it only exposes information that is typically accessible to project members in Azure DevOps.

From the tool's definition Tool name is 'list_pull_requests' and description states 'List all pull requests in the project' — a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list_pull_requests gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for list_pull_requests:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_pull_requests": {}
  }
}

list_pull_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Azure DevOps MCP Server for Cline — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_pull_requests tool do? +

List all pull requests in the project. It is categorised as a Read tool in the Azure DevOps MCP Server for Cline MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_pull_requests? +

Register the Azure DevOps MCP Server for Cline 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 for Cline. Nothing to install.

What risk level is list_pull_requests? +

list_pull_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_pull_requests? +

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.

How do I block list_pull_requests completely? +

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.

What MCP server provides list_pull_requests? +

list_pull_requests is provided by the Azure DevOps MCP Server for Cline MCP server (stefanskiasan/azure-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Azure DevOps MCP Server for Cline tool call.

Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.