update_pull_request_branch · Server Puppeteer MCP

WHAT IT DOES

What update_pull_request_branch does on Server Puppeteer

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

WHY IT NEEDS A POLICY

Why update_pull_request_branch needs a policy

This tool modifies a pull request branch by updating it with latest changes from the base branch. While it does not delete or irreversibly destroy data (thus not Destructive), it does alter version control state in a way that could affect code review and collaboration. The change is reversible through git operations.

From the tool's definition The tool description states 'Update a pull request branch' which modifies branch state by integrating latest changes from the base branch. This is a write operation that changes the branch's commit history and content.

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 Server Puppeteer, 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 Server Puppeteer 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 Server Puppeteer 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 Server Puppeteer. 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 Server Puppeteer MCP server (@hisma/server-puppeteer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.