git_workspace · Git MCP: Risk & Policy

WHAT IT DOES

What git_workspace does on Git

AI agents invoke git_workspace 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_workspace needs a policy

This tool performs a wide range of Git operations that modify repository state in complex ways. Rebase, merge, and cherry-pick alter commit history and working tree; stash moves changes; submodule and worktree operations affect repository structure. While some actions are reversible, these operations can cause data loss (e.g., dropped stashes, rebase conflicts overwriting history) and span multiple severity levels.

From the tool's definition stash/rebase/cherry-pick/merge/bisect/tag/worktree/submodule actions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_workspace Rate-limited

git_workspace 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_workspace": {
      "limits": [
        {
          "counter": "git_workspace_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_workspace

What does the git_workspace tool do? +

Workspace tool for stash/rebase/cherry-pick/merge/bisect/tag/worktree/submodule actions plus stash_all shortcut. 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_workspace? +

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

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

Can I rate-limit git_workspace? +

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

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

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