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

WHAT IT DOES

What git-add does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why git-add needs a policy

git-add stages file changes for commit but does not delete data or execute arbitrary code. The change is reversible (files can be unstaged via git-reset). This is a classic Write operation—creating or modifying state without side effects that cannot be undone. Severity is low because staging area modifications have minimal blast radius if misused; a developer can easily unstage files or amend commits.

From the tool's definition Tool description states it 'Adds a specific file to the staging area' — this modifies the Git staging index, a reversible change. The sibling tools on this server (git-commit, git-checkout, git-diff, etc.) confirm a Write-focused Git workflow context.

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

FAQ

Questions about git-add

What does the git-add tool do? +

Adds a specific file to the staging area. It is categorised as a Write tool in the GitHub 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 GitHub 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 GitHub 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 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.