Create a new branch in a GitHub repository
AI agents use create_branch to create or update resources in Server Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Github environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (username or organization) |
branch | string | Yes | Name for the new branch |
from_branch | string | — | Optional: source branch to create from (defaults to the repository's default branch) |
Parameters from the server's own tool schema.
Creating a branch is a reversible modification operation—branches can be deleted and the repository state restored. It does not delete data, execute code, or move funds. While it could enable subsequent harmful actions (like pushing malicious code), the tool itself only creates a reference. This is clearly Write rather than Execute or Destructive.
From the tool's definition Tool creates a new branch in a GitHub repository. 'Create' indicates a write operation that modifies repository structure by adding a new branch reference.
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 Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_branch accepts 4 parameters: repo, owner, branch, from_branch. Required: repo, owner, branch. The full parameter table on this page comes from the server's own tool schema.
Register the Server Github 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 Github. 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 Github MCP server (@iflow-mcp/server-github). 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 →