get_discussion_comments
Get comments from a discussion
This record as markdown: /tools/github/get-discussion-comments.md
What get_discussion_comments does on GitHub
AI agents call get_discussion_comments to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | — | Repository name |
after | string | — | Cursor for pagination. Use the endCursor from the previous page's PageInfo for GraphQL APIs. |
owner | string | — | Repository owner |
perPage | number | — | Results per page for pagination (min 1, max 100) |
discussionNumber | number | — | Discussion Number |
Parameters from the server's own tool schema.
Why get_discussion_comments is rated Low
This tool retrieves existing discussion comments without modifying, deleting, or executing any operations. It is a simple read operation with no side effects on data or external systems. The low severity reflects minimal risk even if misused by an agent, as it only exposes data already visible in GitHub discussions.
From the tool's definition Tool name 'get_discussion_comments' and description 'Get comments from a discussion' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_discussion_comments 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 get_discussion_comments, this is the rule to start with:
get_discussion_comments is read-only, so it stays allowed. 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 get_discussion_comments call is checked against it from then on.
Questions about get_discussion_comments
Get comments from a discussion. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_discussion_comments accepts 5 parameters: repo, after, owner, perPage, discussionNumber. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_discussion_comments: 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.
get_discussion_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_discussion_comments 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 get_discussion_comments. 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.
get_discussion_comments is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.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