gh_pull_requests · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What gh_pull_requests does on RedisNexus

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

WHY IT NEEDS A POLICY

Why gh_pull_requests needs a policy

While this tool includes read operations (list, view, diff, checks), its core capabilities—create, merge, close, reopen—modify repository state reversibly. Merging PRs is especially high-risk in a production context as it can deploy code changes. This is Write rather than Execute because the tool itself doesn't run arbitrary code; it manages PR state.

From the tool's definition Tool description states it can 'create, merge, close, reopen, review' pull requests. Creating and merging PRs modifies the codebase and repository state reversibly, which is a Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gh_pull_requests Rate-limited

gh_pull_requests 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": {
    "gh_pull_requests": {
      "limits": [
        {
          "counter": "gh_pull_requests_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 RedisNexus, so you can run agents against it safely.

FAQ

Questions about gh_pull_requests

What does the gh_pull_requests tool do? +

Manage pull requests: list, view, create, merge, close, reopen, review, diff, checks. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gh_pull_requests? +

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

What risk level is gh_pull_requests? +

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

Can I rate-limit gh_pull_requests? +

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

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

gh_pull_requests is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.