add_issue_comment

THE RISK

Medium Risk

Why add_issue_comment needs a policy

Adding an issue comment creates data (the comment text) that becomes part of a GitHub issue's discussion thread. This is a Write operation because: (1) it modifies state by appending new content to an issue, (2) the action is reversible (comments can be edited or deleted), and (3) it does not irreversibly destroy data or execute arbitrary code.

From the tool's definition Tool description states 'Add a comment to an existing GitHub Issue' — this creates new content (a comment) that is reversibly modifiable and deletable, consistent with Write category behavior.

Documented attack patterns abuse exactly the kind of access add_issue_comment gives an agent:

POLICY

How to control add_issue_comment

PolicyLayer is an MCP gateway — it sits between your AI agents and Gitbridge, and nothing reaches the server without passing your rules. This is the rule we recommend for add_issue_comment:

policy.json

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

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

Create a free account and register Gitbridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gitbridge tools

Destructive delete_file Delete a file from a GitHub repository. This is a destructive operation — the file will be Write create_issue Create a new GitHub Issue in a repository Write create_repo Create a new GitHub repository on a personal account or within an organization Write flush_queue Commit all queued writes for a repository in a single GitHub commit. Call queue_write firs Write move_file Move or rename a file. Reads from old path, writes to new path, then returns a GitHub link Write push_multiple_files Create or update multiple files in a single commit using the Git Data API Write queue_write Queue a file write for batch commit. Writes are held in server memory and flushed together Write update_issue Update an existing GitHub Issue (change status, labels, title, or body)

All 16 Gitbridge tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_issue_comment

What does the add_issue_comment tool do? +

Add a comment to an existing GitHub Issue. It is categorised as a Write tool in the Gitbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_issue_comment? +

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

What risk level is add_issue_comment? +

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

Can I rate-limit add_issue_comment? +

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

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

add_issue_comment is provided by the Gitbridge MCP server (iotus/gitbridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitbridge tool call.

Start from Gitbridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →