Fetch all comments (review comments and issue comments) added by a user for a given repository within a time duration. Combines PR review comments (inline comments from PR reviews) and PR issue comments (general comments on PRs), normalizes them into a unified format, and deduplicates by comment ...
AI agents call github.getUserComments 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.
This tool performs read-only queries against GitHub data to retrieve historical comments authored by a user within specified repositories and time ranges. It retrieves existing data for analysis and reporting purposes without creating, modifying, or deleting any resources. The operations are purely informational and have no side effects. It fits the 'Read' category: retrieves or queries data with no side effects.
From the tool's definition Tool description states it 'Fetch[es] all comments' and 'get[s] a complete view of all user comments' with filtering capabilities. The verbs used are passive data retrieval operations: 'Fetch', 'Combines', 'normalizes', 'Filters', 'deduplicates'.
Attacks that exploit this kind of access
Fetch all comments (review comments and issue comments) added by a user for a given repository within a time duration. Combines PR review comments (inline comments from PR reviews) and PR issue comments (general comments on PRs), normalizes them into a unified format, and deduplicates by comment ID. Filters by comment.createdAt and author. Automatically filters out auto-generated comments and comments on auto-created PRs. Use this tool to get a complete view of all user comments in a repository. Example use cases: - Get all comments by a user in a repository for analysis - Track comment activity and engagement - Analyze comment patterns and types - Extract all user feedback for sentiment analysis Returns: Array of comment objects with id, body, createdAt, author, prId, prNumber, prTitle, prRepo, commentType (review/issue), filePath, lineNumber, reviewId. 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 github.getUserComments: 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.
github.getUserComments 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 github.getUserComments 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 github.getUserComments. 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.
github.getUserComments is provided by the GitHub MCP Server MCP server (radireddy/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 →