Retrieves all threads and comments on a PR.
AI agents call git.pr.comment.list to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves/lists comments and threads on a pull request. It performs no modifications, deletions, or external operations. The verb 'retrieves' and the read-only nature of listing existing comments clearly places this in the Read category with low severity, as it has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'git.pr.comment.list' and description 'Retrieves all threads and comments on a PR' indicate a read-only operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
Retrieves all threads and comments on a PR. 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 git.pr.comment.list: 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.
git.pr.comment.list 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 git.pr.comment.list 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 git.pr.comment.list. 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.
git.pr.comment.list is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). 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 →