git_get_pull_requests

Gets a list of pull requests in a repository with filtering options

Server Azure DevOps Multi-Organization MCP Server nikydobrev/mcp-server-azure-devops-multi
Category Read
Risk class Low
Parameters 00 required

What git_get_pull_requests does on Azure DevOps Multi-Organization MCP Server

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

Why git_get_pull_requests needs a policy

This tool queries and retrieves pull request data from a repository. The use of 'Gets a list' with 'filtering options' clearly describes a read-only operation that does not modify, execute, or delete any data. The blast radius of misuse is minimal—an agent could retrieve pull request information it shouldn't access, but cannot modify repositories, execute code, or cause data loss.

From the tool's definition Tool name 'git_get_pull_requests' and description 'Gets a list of pull requests in a repository with filtering options' indicate a retrieval operation with no side effects.

Questions about git_get_pull_requests

What does the git_get_pull_requests tool do? +

Gets a list of pull requests in a repository with filtering options. It is categorised as a Read tool in the Azure DevOps Multi-Organization MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_get_pull_requests? +

Register the Azure DevOps Multi-Organization MCP Server MCP server in PolicyLayer and add a rule for git_get_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 Multi-Organization MCP Server. Nothing to install.

What risk level is git_get_pull_requests? +

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

Can I rate-limit git_get_pull_requests? +

Yes. Add a rate_limit block to the git_get_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 git_get_pull_requests completely? +

Set action: deny in the PolicyLayer policy for git_get_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 git_get_pull_requests? +

git_get_pull_requests is provided by the Azure DevOps Multi-Organization MCP Server MCP server (nikydobrev/mcp-server-azure-devops-multi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.