git · MCP Build Environment Service MCP: Risk & Policy

WHAT IT DOES

What git does on MCP Build Environment Service

AI agents invoke git to trigger actions in MCP Build Environment Service. 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 needs a policy

Git commands span multiple operation types (read, write, destructive) depending on arguments: `git log` is read-only, but `git push --force` can overwrite remote history, `git reset --hard` can destroy local work, and `git clone` can execute arbitrary code from repository hooks.

From the tool's definition Tool description states 'Run git commands in a repository' - this executes arbitrary git operations whose effects depend on arguments provided by the AI agent.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git Rate-limited

git 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": {
      "limits": [
        {
          "counter": "git_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 Build Environment Service, so you can run agents against it safely.

FAQ

Questions about git

What does the git tool do? +

Run git commands in a repository. It is categorised as a Execute tool in the MCP Build Environment Service 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? +

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

What risk level is git? +

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

Can I rate-limit git? +

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

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

git is provided by the MCP Build Environment Service MCP server (jbroll/mcp-build). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.