git_workflow · Git MCP: Risk & Policy

WHAT IT DOES

What git_workflow does on Git

AI agents invoke git_workflow 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_workflow needs a policy

This is Execute rather than Write because it executes multi-step workflows whose side effects are not simply 'create or modify data reversibly' but depend on arbitrary workflow logic. While individual workflow steps might be Write operations (commits, pushes), the tool itself runs/executes them.

From the tool's definition Tool description states 'Run named multi-step Git workflows' — the verb 'Run' indicates execution of potentially complex, multi-step operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_workflow Rate-limited

git_workflow 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_workflow": {
      "limits": [
        {
          "counter": "git_workflow_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_workflow

What does the git_workflow tool do? +

Run named multi-step Git workflows with resumable lifecycle controls. 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_workflow? +

Register the Git MCP server in PolicyLayer and add a rule for git_workflow: 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_workflow? +

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

Can I rate-limit git_workflow? +

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

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

git_workflow 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.