Fetches all active comment threads from an Azure DevOps Pull Request.
AI agents call ado_pr_threads to retrieve information from Git Stuff 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 comment thread data from a pull request without creating, modifying, or deleting anything. It is a read-only query operation with minimal security impact—exposing PR comments does not compromise system integrity or enable destructive actions.
From the tool's definition Tool name and description: 'Fetches all active comment threads from an Azure DevOps Pull Request' — the verb 'Fetches' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetches all active comment threads from an Azure DevOps Pull Request. It is categorised as a Read tool in the Git Stuff Server MCP Server, which means it retrieves data without modifying state.
Register the Git Stuff Server MCP server in PolicyLayer and add a rule for ado_pr_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 Git Stuff Server. Nothing to install.
ado_pr_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 ado_pr_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 ado_pr_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.
ado_pr_threads is provided by the Git Stuff Server MCP server (skurekjakub/gitstuffserver). 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 →