get_discussion_comments
AI agents call get_discussion_comments to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly indicates a read-only operation that retrieves discussion comments from GitHub. There is no evidence of data modification, deletion, or execution of arbitrary code. The low severity reflects the minimal risk of misuse—fetching discussion comments cannot harm repository integrity or trigger unintended operations.
From the tool's definition Tool name 'get_discussion_comments' contains 'get', which indicates a retrieval operation. The empty description limits certainty, but the naming convention and context within a GitHub API server (alongside tools like 'create_issue_comment', 'create_branch')…
Attacks that exploit this kind of access
get_discussion_comments. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server 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 MCP Server. 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 MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →