git_add

A write tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/git-add.md

WHAT IT DOES

What git_add does on GitHub

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

RISK

Why git_add is rated Medium

The git add command stages file changes for commit. While this creates or modifies the staging state (Write category), it is reversible and does not permanently alter the repository or delete data. It affects local git state and could lead to unintended commits if misused by an agent, hence medium severity.

From the tool's definition Tool name 'git_add' and description 'Git add' indicate the standard git staging operation that prepares changes for commit. This modifies the index/staging area, which is reversible through 'git reset'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_add safely

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

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.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every git_add call is checked against it from then on.

FAQ

Questions about git_add

What does the git_add tool do? +

git_add is a write tool on the GitHub MCP server. It is categorised as a Write tool in the GitHub 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 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. 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 (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →