update-pull-request-branch

WHAT IT DOES

What update-pull-request-branch does on GitHub Enterprise MCP Server

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

WHY IT NEEDS A POLICY

Why update-pull-request-branch needs a policy

This tool modifies repository state by updating a branch (likely via merge or rebase), which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), nor involve financial transactions (not Financial).

From the tool's definition Tool name 'update-pull-request-branch' and description 'Update a pull request branch with the latest changes from the base branch' indicate modification of branch state through a merge/rebase operation.

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 Enterprise 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 a pull request branch with the latest changes from the base branch. It is categorised as a Write tool in the GitHub Enterprise 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 Enterprise 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 Enterprise 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 Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.