Create a new branch in a GitHub repository
AI agents use create_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.
This tool creates new data (a git branch) in a GitHub repository, which is a reversible modification. It does not execute arbitrary code, delete data, or involve financial transactions. While it modifies repository state, branches can be deleted if created in error, making it Write rather than Destructive.
From the tool's definition Tool is named 'create_branch' and described as 'Create a new branch in a GitHub repository'. Creating a branch is a write operation that modifies repository state by adding a new ref, but does not delete or overwrite existing data irreversibly.
Attacks that exploit this kind of access
Create a new branch in a GitHub repository. 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.
Register the Server Puppeteer MCP server in PolicyLayer and add a rule for create_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.
create_branch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →