List comments on an issue or pull request conversation (general comments, not inline diff review comments). Pass a PR number as issue_number to fetch conversation-tab comments on a PR.
AI agents call list_issue_comments to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing comments from GitHub issues or PRs without modifying, creating, deleting, or executing any operations. It is a straightforward data retrieval action with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List comments on an issue or pull request' — a retrieval operation with no side effects. The verb 'list' and context of fetching existing conversation data confirms read-only access.
Attacks that exploit this kind of access
List comments on an issue or pull request conversation (general comments, not inline diff review comments). Pass a PR number as issue_number to fetch conversation-tab comments on a PR. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github MCP server in PolicyLayer and add a rule for list_issue_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 Mcp Github. Nothing to install.
list_issue_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 list_issue_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 list_issue_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.
list_issue_comments is provided by the Mcp Github MCP server (@missionsquad/mcp-github). 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 →