Low Risk

list_pr_reviews

List PR reviews and their approval status.

How to control list_pr_reviews ↓

What list_pr_reviews does on GitHub Repos Manager MCP Server

AI agents call list_pr_reviews to retrieve information from GitHub Repos Manager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_pr_reviews needs a policy

This tool queries and retrieves existing PR review data and approval statuses. It performs no mutations, executions, or destructive operations. It is a straightforward read operation on GitHub pull request review metadata.

From the tool's definition Tool name 'list_pr_reviews' and description 'List PR reviews and their approval status' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list_pr_reviews gives an agent:

How to control list_pr_reviews

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Repos Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_pr_reviews:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_pr_reviews": {}
  }
}

list_pr_reviews is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GitHub Repos Manager MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_pr_reviews

What does the list_pr_reviews tool do? +

List PR reviews and their approval status. It is categorised as a Read tool in the GitHub Repos Manager MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_pr_reviews? +

Register the GitHub Repos Manager MCP Server MCP server in PolicyLayer and add a rule for list_pr_reviews: 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 Repos Manager MCP Server. Nothing to install.

What risk level is list_pr_reviews? +

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

Can I rate-limit list_pr_reviews? +

Yes. Add a rate_limit block to the list_pr_reviews 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 list_pr_reviews completely? +

Set action: deny in the PolicyLayer policy for list_pr_reviews. 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 list_pr_reviews? +

list_pr_reviews is provided by the GitHub Repos Manager MCP Server MCP server (kurdin/github-repos-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub Repos Manager MCP Server tool call.

Start from GitHub Repos Manager MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

84 GitHub Repos Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.