AI agents use swarm_git_create_branch to create or update resources in Mcp Swarm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Swarm environment.
Creating a Git branch is a write operation that modifies the repository state by introducing a new branch reference. While reversible (branches can be deleted), it changes the repository structure. This is a Write operation rather than Read (it modifies state) or Destructive (it can be undone).
From the tool's definition Tool name 'swarm_git_create_branch' and description '创建新的 Git 分支' (create a new Git branch) indicate a modification operation that creates new repository branches.
Attacks that exploit this kind of access
创建新的 Git 分支。. It is categorised as a Write tool in the Mcp Swarm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Swarm MCP server in PolicyLayer and add a rule for swarm_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 Mcp Swarm. Nothing to install.
swarm_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 swarm_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 swarm_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.
swarm_git_create_branch is provided by the Mcp Swarm MCP server (moselu/mcp-swarm). 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 →