Add a comment to a pull request (repositoryId optional; derived from pullRequestId when omitted)
AI agents use add_pull_request_comment 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 new data (a comment) on an existing pull request, which is a reversible write operation. Comments can be edited or deleted later. There is no data deletion, code execution, financial impact, or destructive action. The blast radius is minimal—an errant comment is easily remediated.
From the tool's definition Tool name 'add_pull_request_comment' and description 'Add a comment to a pull request' indicate creation of new comment data on an existing pull request resource.
Documented attack patterns abuse exactly the kind of access add_pull_request_comment 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 add_pull_request_comment:
{
"version": "1",
"default": "deny",
"tools": {
"add_pull_request_comment": {
"limits": [
{
"counter": "add_pull_request_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_pull_request_comment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a comment to a pull request (repositoryId optional; derived from pullRequestId when omitted). 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 add_pull_request_comment: 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.
add_pull_request_comment 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 add_pull_request_comment 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 add_pull_request_comment. 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.
add_pull_request_comment 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.