Get all comment threads in a pull request. Returns thread details including comments, status, relationships, and file annotations. Supports both file-specific and general comments. Results include thread context and metadata.
AI agents call azure_devops_pull_request_threads to retrieve information from Cursor Azure Devops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing pull request comment thread data from Azure DevOps. It performs no creation, modification, deletion, or execution of code/commands. The retrieval of PR discussion history and metadata is a read-only operation with minimal security risk — worst case an agent could view sensitive discussion content, but cannot alter or destroy it.
From the tool's definition Tool name and description use 'Get all comment threads' which retrieves data without modification. Returns 'thread details including comments, status, relationships, and file annotations' — purely informational access to PR discussion metadata with no side…
Documented attack patterns abuse exactly the kind of access azure_devops_pull_request_threads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for azure_devops_pull_request_threads:
{
"version": "1",
"default": "deny",
"tools": {
"azure_devops_pull_request_threads": {}
}
}azure_devops_pull_request_threads 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 all comment threads in a pull request. Returns thread details including comments, status, relationships, and file annotations. Supports both file-specific and general comments. Results include thread context and metadata. It is categorised as a Read tool in the Cursor Azure Devops MCP Server, which means it retrieves data without modifying state.
Register the Cursor Azure Devops MCP server in PolicyLayer and add a rule for azure_devops_pull_request_threads: 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 Cursor Azure Devops. Nothing to install.
azure_devops_pull_request_threads 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 azure_devops_pull_request_threads 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 azure_devops_pull_request_threads. 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.
azure_devops_pull_request_threads is provided by the Cursor Azure Devops MCP server (maximtitovich/cursor-azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cursor Azure Devops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Cursor Azure Devops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.