AI agents use ado_create_pull_request_thread to create or update resources in Mcp Azure — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Azure environment.
This tool creates new pull request comment threads, which is a reversible write operation. It does not delete, execute arbitrary code, move money, or cause irreversible changes. The medium severity reflects that while comments can influence code review decisions, they are non-destructive and can be edited or deleted.
From the tool's definition Tool name 'ado_create_pull_request_thread' and description 'Crea un nuevo hilo de comentarios' (Creates a new comment thread) indicate the tool creates new data—comment threads—in Azure DevOps pull requests.
Attacks that exploit this kind of access
Crea un nuevo hilo de comentarios (comentario general o comentario de código). It is categorised as a Write tool in the Mcp Azure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_create_pull_request_thread: 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 Mcp Azure. Nothing to install.
ado_create_pull_request_thread is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ado_create_pull_request_thread 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_create_pull_request_thread. 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_create_pull_request_thread is provided by the Mcp Azure MCP server (soulberto/mcp-azure). 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 →