Creates an inline code review comment thread on a file and line number in a PR.
AI agents use git.pr.comment.create to create or update resources in Azure DevOps MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server environment.
This tool creates a new comment thread on a pull request, which is a reversible write operation. Comments can typically be edited or deleted, so this is not destructive. The blast radius is medium as misuse could pollute PR reviews with unwanted comments, but it does not modify code or critical resources.
From the tool's definition Creates an inline code review comment thread on a file and line number in a PR
Attacks that exploit this kind of access
Creates an inline code review comment thread on a file and line number in a PR. It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for git.pr.comment.create: 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.create 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 git.pr.comment.create 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.create. 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.create 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 →