create_branch · Kepler MCP GitLab Server MCP: Risk & Policy

WHAT IT DOES

What create_branch does on Kepler MCP GitLab Server

AI agents use create_branch to create or update resources in Kepler MCP GitLab Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kepler MCP GitLab Server environment.

WHY IT NEEDS A POLICY

Why create_branch needs a policy

Creating a branch is a Write operation—it creates a new reference in the repository but is reversible (branches can be deleted). It does not execute arbitrary code, is not destructive, and has no financial impact. Severity is medium because a compromised agent could create many branches or branches with misleading names to disrupt workflow, but the blast radius is contained to repository state and is recoverable.

From the tool's definition Tool name 'create_branch' combined with server context showing it manages 'branches' across GitLab instances. The sibling tools create_file, create_issue, and create_merge_request are all Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_branch Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_branch": {
      "limits": [
        {
          "counter": "create_branch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kepler MCP GitLab Server, so you can run agents against it safely.

FAQ

Questions about create_branch

What does the create_branch tool do? +

create_branch. It is categorised as a Write tool in the Kepler MCP GitLab Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_branch? +

Register the Kepler MCP GitLab 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 Kepler MCP GitLab Server. Nothing to install.

What risk level is create_branch? +

create_branch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_branch? +

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.

How do I block create_branch completely? +

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.

What MCP server provides create_branch? +

create_branch is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.