submit_pull_request_review · Mcp Github MCP: Risk & Policy

WHAT IT DOES

What submit_pull_request_review does on Mcp Github

AI agents use submit_pull_request_review to create or update resources in Mcp Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Github environment.

WHY IT NEEDS A POLICY

Why submit_pull_request_review needs a policy

This tool creates or modifies pull request review records, which is fundamentally a Write operation. While reviews influence code merge decisions and workflow, they do not execute code, delete data, or move money. The severity is medium because misuse could disrupt development workflows, approve dangerous changes, or block legitimate PRs, but the effects are reversible through review edits or dismissals.

From the tool's definition The tool description explicitly states it can 'Submit a pull request review (approve, request changes, or comment)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_pull_request_review Rate-limited

submit_pull_request_review stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_pull_request_review": {
      "limits": [
        {
          "counter": "submit_pull_request_review_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Github, so you can run agents against it safely.

FAQ

Questions about submit_pull_request_review

What does the submit_pull_request_review tool do? +

Submit a pull request review (approve, request changes, or comment). It is categorised as a Write tool in the Mcp Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_pull_request_review? +

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

What risk level is submit_pull_request_review? +

submit_pull_request_review is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_pull_request_review? +

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

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

submit_pull_request_review is provided by the Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.