Create a new branch in a GitHub repository
AI agents use create-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.
Creating a branch is a standard Write operation—it modifies repository state by introducing a new branch object, but this is fully reversible (the branch can be deleted). It does not execute arbitrary code, delete data irreversibly, or move funds. The blast radius is minimal; a mistaken branch creation has no financial impact and can be easily cleaned up.
From the tool's definition Tool name 'create-branch' and description 'Create a new branch in a GitHub repository' indicate a reversible, non-destructive write operation that creates a new git branch.
Attacks that exploit this kind of access
Create a new branch in a GitHub repository. 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.
Register the GitHub Enterprise MCP Server 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 GitHub Enterprise MCP Server. 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 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.
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 →