reviewers

GitHub usernames to request reviews from (string[], optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/reviewers.md

WHAT IT DOES

What reviewers does on GitHub

AI agents call reviewers as a supporting operation in GitHub workflows.

RISK

Why reviewers is rated Low

The description reads like a parameter definition for another tool rather than an independent tool with its own action. It does not describe a retrieving, writing, executing, or destructive operation on its own. Without a clear action associated with this tool, it cannot be confidently categorized beyond 'Other'. Confidence is low due to the uninformative description.

From the tool's definition Tool description is 'GitHub usernames to request reviews from (string[], optional)' — this appears to be a parameter descriptor, not a standalone tool with defined behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reviewers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reviewers, this is the rule to start with:

reviewers Rate-limited

reviewers gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reviewers": {
      "limits": [
        {
          "counter": "reviewers_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every reviewers call is checked against it from then on.

FAQ

Questions about reviewers

What does the reviewers tool do? +

GitHub usernames to request reviews from (string[], optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on reviewers? +

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

What risk level is reviewers? +

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

Can I rate-limit reviewers? +

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

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

reviewers is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →