Create a new branch in a GitHub repository.
AI agents use createBranch to create or update resources in GitHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.
Creating a branch is a write operation that adds new structure to a repository. It is reversible (branches can be deleted), so it does not qualify as Destructive. The blast radius is medium because unauthorized branch creation could pollute the repository namespace, interfere with workflows, or serve as a staging point for malicious changes, but the impact is containable and does not directly delete data or execute…
From the tool's definition Tool name 'createBranch' and description 'Create a new branch in a GitHub repository' indicate a reversible creation operation that modifies repository structure.
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 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for createBranch: 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 MCP Server. Nothing to install.
createBranch 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 createBranch 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 createBranch. 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.
createBranch is provided by the GitHub MCP Server MCP server (j-nowcow/github-mcp-practice). 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 →