git_branch · MCP Workspace Server MCP: Risk & Policy

WHAT IT DOES

What git_branch does on MCP Workspace Server

AI agents invoke git_branch to trigger actions in MCP Workspace Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why git_branch needs a policy

While listing branches is a Read operation, creating and switching branches modifies repository state (HEAD pointer, working tree) and managing branches can include deleting them. Since the tool spans multiple categories, the most severe applicable is Execute, as it triggers external git operations with side effects.

From the tool's definition 'List, create, switch, and manage git branches' — involves executing git operations that alter repository state (creating branches, switching HEAD)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_branch Rate-limited

git_branch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_branch": {
      "limits": [
        {
          "counter": "git_branch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about git_branch

What does the git_branch tool do? +

List, create, switch, and manage git branches. It is categorised as a Execute tool in the MCP Workspace Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_branch? +

Register the MCP Workspace Server MCP server in PolicyLayer and add a rule for git_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 Workspace Server. Nothing to install.

What risk level is git_branch? +

git_branch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit git_branch? +

Yes. Add a rate_limit block to the git_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 git_branch completely? +

Set action: deny in the PolicyLayer policy for git_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 git_branch? +

git_branch is provided by the MCP Workspace Server MCP server (shayyeffet/ultimate_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.