github.getPRReviews

Fetch all PR reviews submitted by a user within a time range, filtered by repository. Returns review state (APPROVED, CHANGES_REQUESTED, COMMENTED), PR details, and submission timestamps. Automatically filters out reviews on auto-generated PRs. Use this tool to assess code review participation an...

Server GitHub MCP Server radireddy/github-mcp
Category Read
Risk class Low
Parameters 00 required

What github.getPRReviews does on GitHub MCP Server

AI agents call github.getPRReviews 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.

Why github.getPRReviews needs a policy

This tool exclusively retrieves historical data about code reviews without side effects. It queries GitHub for review metadata and analysis only. The stated purpose is performance assessment and impact analysis through data retrieval, which is characteristic of Read category tools. No write, destructive, execute, or financial actions are possible.

From the tool's definition Tool description states 'Fetch all PR reviews' and 'Returns review state, PR details, and submission timestamps.' The use cases include 'Measure code review engagement,' 'Analyze review patterns,' and 'Track review activity over time'—all read-only operations.

Questions about github.getPRReviews

What does the github.getPRReviews tool do? +

Fetch all PR reviews submitted by a user within a time range, filtered by repository. Returns review state (APPROVED, CHANGES_REQUESTED, COMMENTED), PR details, and submission timestamps. Automatically filters out reviews on auto-generated PRs. Use this tool to assess code review participation and review quality. Example use cases: - Measure code review engagement (how many PRs reviewed) - Analyze review patterns (approval vs. change requests) - Track review activity over time - Assess code review contribution for performance evaluations Returns: Array of review objects with id, state, prId, prNumber, prTitle, prRepo, submittedAt. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github.getPRReviews? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for github.getPRReviews: 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.

What risk level is github.getPRReviews? +

github.getPRReviews is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github.getPRReviews? +

Yes. Add a rate_limit block to the github.getPRReviews 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.

How do I block github.getPRReviews completely? +

Set action: deny in the PolicyLayer policy for github.getPRReviews. 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.

What MCP server provides github.getPRReviews? +

github.getPRReviews 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.