commentId
The ID of the comment to reply to. Use the CommentID field from get_review_comments. (number, required)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/commentid.md
What commentId does on GitHub
AI agents call commentId as a supporting operation in GitHub workflows.
Why commentId is rated Low
This appears to be a parameter descriptor rather than an independent tool — it describes an input field (a comment ID) for another operation. It has no standalone action or side effect of its own. The description is uninformative as a tool definition, lowering confidence. Classified as Other since it does not perform any operation by itself.
From the tool's definition Tool description: 'The ID of the comment to reply to. Use the CommentID field from get_review_comments. (number, required)'
Attacks that exploit this kind of access
The rule that runs commentId 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 commentId, this is the rule to start with:
commentId gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every commentId call is checked against it from then on.
Questions about commentId
The ID of the comment to reply to. 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.
Register the GitHub MCP server in PolicyLayer and add a rule for commentId: 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.
commentId is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the commentId 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.
Set action: deny in the PolicyLayer policy for commentId. 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.
commentId 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue