update_pull_request_branch · GitHub MCP Server MCP

WHAT IT DOES

What update_pull_request_branch does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why update_pull_request_branch needs a policy

The tool updates an existing pull request's branch, which is a reversible modification operation. This falls under Write category rather than Destructive (not irreversible) or Execute (not arbitrary code execution). Severity is high because misconfigured branch updates could disrupt development workflows, merge conflicts, or cause unintended changes to pull request targets.

From the tool's definition Tool name 'update_pull_request_branch' indicates modification of pull request branch state. Sibling tools like 'create_or_update_file', 'create_commit_status', and 'create_branch' on the same GitHub MCP server are Write/Execute operations that create or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pull_request_branch Rate-limited

update_pull_request_branch 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": {
    "update_pull_request_branch": {
      "limits": [
        {
          "counter": "update_pull_request_branch_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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about update_pull_request_branch

What does the update_pull_request_branch tool do? +

update_pull_request_branch. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_pull_request_branch? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for update_pull_request_branch: 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 update_pull_request_branch? +

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

Can I rate-limit update_pull_request_branch? +

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

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

update_pull_request_branch is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.