create_pull_request_comment · azure-devops MCP Server MCP

WHAT IT DOES

What create_pull_request_comment does on azure-devops MCP Server

AI agents use create_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 IT NEEDS A POLICY

Why create_pull_request_comment needs a policy

This tool creates new data (a comment) in a reversible manner. It does not execute code, delete data, or move money. While comments can influence CI/CD decisions or code reviews, the action itself is a standard write operation that can be edited or deleted.

From the tool's definition Tool name 'create_pull_request_comment' and description 'Add a comment to a pull request' indicate creation of new content that modifies pull request state by appending a comment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_pull_request_comment Rate-limited

create_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_pull_request_comment": {
      "limits": [
        {
          "counter": "create_pull_request_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches azure-devops MCP Server, so you can run agents against it safely.

FAQ

Questions about create_pull_request_comment

What does the create_pull_request_comment tool do? +

Add a comment to a pull request. 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.

How do I enforce a policy on create_pull_request_comment? +

Register the azure-devops MCP Server MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_pull_request_comment? +

create_pull_request_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_pull_request_comment? +

Yes. Add a rate_limit block to the create_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.

How do I block create_pull_request_comment completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_pull_request_comment? +

create_pull_request_comment is provided by the azure-devops MCP Server MCP server (mmruesch12/azdo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.