git_flow · Git MCP: Risk & Policy

WHAT IT DOES

What git_flow does on Git

AI agents invoke git_flow to trigger actions in Git. 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_flow needs a policy

Git Flow workflows involve multiple git operations (branch creation, merges, tags, pushes) chained together. This is an Execute-level tool because it triggers complex external git operations. Severity is high because misuse could create incorrect branch structures, merge unintended code, or push tags/releases to remote repositories.

From the tool's definition 'Implements git-flow-next-style workflows directly' — executes branching, merging, tagging, and release workflows as composite git operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_flow Rate-limited

git_flow 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_flow": {
      "limits": [
        {
          "counter": "git_flow_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 Git, so you can run agents against it safely.

FAQ

Questions about git_flow

What does the git_flow tool do? +

Implements git-flow-next-style workflows directly, without requiring the. It is categorised as a Execute tool in the Git 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_flow? +

Register the Git MCP server in PolicyLayer and add a rule for git_flow: 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 Git. Nothing to install.

What risk level is git_flow? +

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

Can I rate-limit git_flow? +

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

Set action: deny in the PolicyLayer policy for git_flow. 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_flow? +

git_flow is provided by the Git MCP server (selfagency/git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.