git_add · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_add does on Git MCP Server

AI agents use git_add to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.

WHY IT NEEDS A POLICY

Why git_add needs a policy

git_add modifies the staging area (index) by marking file changes for the next commit. This is a reversible Write operation—changes can be unstaged with git_reset or git_restore. It does not execute arbitrary commands, delete data irreversibly, or move money. While it could be part of a workflow leading to commits/pushes, the tool itself only stages content.

From the tool's definition Tool description explicitly states it 'Stage files for commit' and 'Adds file contents to the index (staging area) in preparation for the next commit.' The words 'stage' and 'adds file contents' indicate modification of the git index, which is reversible…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_add Rate-limited

git_add stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_add": {
      "limits": [
        {
          "counter": "git_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about git_add

What does the git_add tool do? +

Stage files for commit. Adds file contents to the index (staging area) in preparation for the next commit. Can stage specific files or all changes in the working directory. IMPORTANT: Always use a full, absolute path to the repository to ensure proper functionality. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_add? +

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

What risk level is git_add? +

git_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git_add? +

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

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

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