issue-comment

Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo.

SERVERGit SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/issue-comment.md

WHAT IT DOES

What issue-comment does on Git

AI agents use issue-comment to create or update resources in Git, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git environment.

RISK

Why issue-comment is rated Medium

This tool creates or modifies comments on issues, which are reversible Write operations. Although deletion is possible, the tool is primarily designed for comment management (add/edit/delete) on a per-comment basis rather than bulk or system-wide destructive operations.

From the tool's definition Tool description states it 'Adds, edits, or deletes a comment on an issue.' The operations of adding and editing are reversible modifications to data (comments).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs issue-comment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For issue-comment, this is the rule to start with:

issue-comment Rate-limited

issue-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": {
    "issue-comment": {
      "limits": [
        {
          "counter": "issue-comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every issue-comment call is checked against it from then on.

FAQ

Questions about issue-comment

What does the issue-comment tool do? +

Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue-comment? +

Register the Git MCP server in PolicyLayer and add a rule for issue-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 Git. Nothing to install.

What risk level is issue-comment? +

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

Can I rate-limit issue-comment? +

Yes. Add a rate_limit block to the issue-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 issue-comment completely? +

Set action: deny in the PolicyLayer policy for issue-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 issue-comment? +

issue-comment is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →