comment_id

Review comment ID to update or delete. Use the CommentID field from get_review_comments. (number, required)

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

Low RISK CLASS

Category Other

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/comment-id.md

WHAT IT DOES

What comment_id does on GitHub

AI agents call comment_id as a supporting operation in GitHub workflows.

RISK

Why comment_id is rated Low

This appears to be a parameter descriptor rather than a standalone tool — it describes an input field (a comment ID) used by other tools that update or delete comments. It does not perform any action on its own. The description is uninformative about any direct operation this 'tool' executes. Classifying as Other with low confidence since this seems misidentified as a tool rather than a parameter.

From the tool's definition Tool description: 'Review comment ID to update or delete. Use the CommentID field from get_review_comments. (number, required)'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comment_id 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 comment_id, this is the rule to start with:

comment_id Rate-limited

comment_id gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comment_id": {
      "limits": [
        {
          "counter": "comment_id_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about comment_id

What does the comment_id tool do? +

Review comment ID to update or delete. Use the CommentID field from get_review_comments. (number, required). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on comment_id? +

Register the GitHub MCP server in PolicyLayer and add a rule for comment_id: 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 comment_id? +

comment_id is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit comment_id? +

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

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

comment_id 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →