Create a new branch in a repository.
AI agents use create_branch to create or update resources in FastMCP GitHub Automation Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FastMCP GitHub Automation Server environment.
Creating a branch is a write operation that modifies repository state by adding a new branch reference. This is reversible (the branch can be deleted) and does not execute arbitrary code, delete data permanently, or move money. It falls clearly into the Write category.
From the tool's definition Tool name 'create_branch' and description 'Create a new branch in a repository' indicate the tool creates a new git branch, which is a reversible modification to repository metadata.
Attacks that exploit this kind of access
Create a new branch in a repository. It is categorised as a Write tool in the FastMCP GitHub Automation Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FastMCP GitHub Automation 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 FastMCP GitHub Automation 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 FastMCP GitHub Automation Server MCP server (siddheshdongare/git-pilot). 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 →