git_create_branch
A write tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/git-create-branch.md
What git_create_branch does on GitHub
AI agents use git_create_branch to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why git_create_branch is rated Medium
Creating a branch is a write operation that modifies repository state reversibly—branches can be deleted and the action does not irreversibly destroy data or execute arbitrary code.
From the tool's definition Tool name 'git_create_branch' and description 'Git create branch' indicate this creates a new git branch, which modifies the repository structure by adding a new branch reference.
Attacks that exploit this kind of access
The rule that runs git_create_branch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_create_branch, this is the rule to start with:
git_create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every git_create_branch call is checked against it from then on.
Questions about git_create_branch
git_create_branch is a write tool on the GitHub MCP server. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP server in PolicyLayer and add a rule for git_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. Nothing to install.
git_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 git_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 git_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.
git_create_branch is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue