add_issue_comment

Add comment to issue

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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-aifity-omnigit-mcp/add-issue-comment.md

WHAT IT DOES

What add_issue_comment does on GitHub

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

RISK

Why add_issue_comment is rated Medium

This tool creates new comment data on GitHub issues, which is a reversible write operation. It does not execute code, delete data, or move money. While comments can be edited or deleted later, the tool itself performs a create operation.

From the tool's definition Tool name: 'add_issue_comment'; description: 'Add comment to issue' — explicitly creates/adds new comment data to an existing issue.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_issue_comment safely

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

add_issue_comment Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_issue_comment": {
      "limits": [
        {
          "counter": "add_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 GitHub, apply this rule, and every add_issue_comment call is checked against it from then on.

FAQ

Questions about add_issue_comment

What does the add_issue_comment tool do? +

Add comment to issue. It is categorised as a Write tool in the GitHub 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 GitHub 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 GitHub. 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 GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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