git_add_all

What git_add_all does on GitHub MCP Server

AI agents use git_add_all 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 git_add_all is rated Medium

git_add_all stages files in Git, creating or modifying the staging area index. This is a Write operation because it alters repository metadata (the staging area) reversibly—changes can be unstaged with git reset. While it doesn't permanently commit or delete data, staging unreviewed files could inadvertently prepare malicious or sensitive changes for commit if an AI agent misuses it in an automated workflow.

From the tool's definition Tool name 'git_add_all' and description 'Adds all files to the staging area' indicate this stages changes for commit, which modifies the repository's state reversibly.

Risk signalsBulk/mass operation — affects multiple targets

The rule that runs git_add_all safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_add_all, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_add_all": {
      "limits": [
        {
          "counter": "git_add_all_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about git_add_all