Get comments for a GitHub issue
AI agents call get_issue_comments to retrieve information from GitHub See MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves existing comments from a GitHub issue without modifying, creating, deleting, or executing any operations. This is a pure read operation with minimal risk; misuse would only allow an AI agent to access information already readable by the authenticated user.
From the tool's definition Tool name is 'get_issue_comments' and description states 'Get comments for a GitHub issue' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get comments for a GitHub issue. It is categorised as a Read tool in the GitHub See MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub See MCP Server MCP server in PolicyLayer and add a rule for get_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 GitHub See MCP Server. Nothing to install.
get_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 get_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 get_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.
get_issue_comments is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). 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 →