Get comments from a specific pull request
AI agents call get_pull_request_comments 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 retrieves existing comments from a pull request without creating, modifying, or deleting any data. It is a straightforward read operation that poses minimal security risk. Even if an AI agent misuses it by fetching comments it shouldn't access, the worst-case scenario is information disclosure, which is lower severity than write or destructive operations.
From the tool's definition Tool name is 'get_pull_request_comments' and description states 'Get comments from a specific pull request' — the verb 'Get' and lack of any modification language indicate a pure data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_pull_request_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pull_request_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_pull_request_comments": {}
}
}get_pull_request_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get comments from a specific pull request. 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 get_pull_request_comments: 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.
get_pull_request_comments 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 get_pull_request_comments 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 get_pull_request_comments. 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.
get_pull_request_comments is provided by the Azure DevOps MCP Server MCP server (tiberriver256/mcp-server-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.