# add_pull_request_comment

A write tool on the Azure DevOps MCP Server MCP server.

Agent View of the PolicyLayer registry record for `add_pull_request_comment`. HTML page: https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/add-pull-request-comment

## Facts

- Tool: `add_pull_request_comment`
- Server: Azure DevOps MCP Server (`abdelrhmansror/azuredevopsmcp`) — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp.md
- Homepage: https://github.com/AbdelrhmanSror/AzureDevopsMcp
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "add_pull_request_comment",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Azure DevOps MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_pull_request_comment": {
      "limits": [
        {
          "counter": "add_pull_request_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Azure DevOps MCP Server (15)

- `get_pull_request` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/get-pull-request.md
- `get_pull_request_full_diff` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/get-pull-request-full-diff.md
- `list_area_paths` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-area-paths.md
- `list_branches` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-branches.md
- `list_iteration_paths` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-iteration-paths.md
- `list_projects` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-projects.md
- `list_pull_requests` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-pull-requests.md
- `list_work_item_types` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/list-work-item-types.md
- `resolve_repo_id` — Read — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/resolve-repo-id.md
- `create_bug` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/create-bug.md
- `create_product_backlog_item` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/create-product-backlog-item.md
- `create_pull_request` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/create-pull-request.md
- `create_work_item` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/create-work-item.md
- `link_pr_to_work_item` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/link-pr-to-work-item.md
- `set_pr_description` — Write — https://policylayer.com/tools/abdelrhmansror-azuredevopsmcp/set-pr-description.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdelrhmansror-azuredevopsmcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdelrhmansror-azuredevopsmcp