git-flow · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git-flow does on GitHub MCP Server

AI agents invoke git-flow to trigger actions in GitHub MCP 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-flow needs a policy

This tool orchestrates multiple Git operations in sequence (add, commit, push), triggering external operations that modify a remote repository. While individual steps like commit are Write, pushing to a remote is an external operation with broad side effects (CI/CD triggers, branch protection bypass risk, exposing code to collaborators).

From the tool's definition Complete Git workflow: add all changes, commit with message, and push to remote

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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about git-flow

What does the git-flow tool do? +

Complete Git workflow: add all changes, commit with message, and push to remote. It is categorised as a Execute tool in the GitHub MCP 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-flow? +

Register the GitHub MCP Server 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 GitHub MCP Server. 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 GitHub MCP Server MCP server (jungchihoon/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.