add_pull_request_comment
A write tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/add-pull-request-comment.md
What add_pull_request_comment does on Azure DevOps MCP Server
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.
Why add_pull_request_comment is rated Medium
Adding comments to pull requests is a reversible write operation that modifies PR metadata/discussions but does not alter code, delete data, or execute arbitrary logic. The blast radius is medium because malicious comments could spam, mislead reviewers, or disrupt workflows, but the action is non-destructive and can be undone by deletion.
From the tool's definition Tool name is 'add_pull_request_comment' which creates/adds a comment to a pull request. The server description confirms the capability to 'add comments' as a write operation on PRs.
Attacks that exploit this kind of access
The rule that runs add_pull_request_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Azure DevOps MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_pull_request_comment, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Azure DevOps MCP Server, apply this rule, and every add_pull_request_comment call is checked against it from then on.
Questions about add_pull_request_comment
add_pull_request_comment is a write tool on the Azure DevOps MCP Server MCP server. 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 (abdelrhmansror/azuredevopsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Azure DevOps MCP Server, and thousands of servers like it.
This server
Across the catalogue