git_add_tool · MCP Git Commit Generator MCP: Risk & Policy

WHAT IT DOES

What git_add_tool does on MCP Git Commit Generator

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

WHY IT NEEDS A POLICY

Why git_add_tool needs a policy

The git add command stages file changes for the next commit—a Write operation that creates/modifies repository state. While reversible (via git reset), it affects repository state and can impact subsequent commits. Severity is medium because the blast radius is limited to the local staging area and requires a subsequent commit to affect the actual repository history.

From the tool's definition Tool is named 'git_add_tool' and operates within a Git repository context alongside commit tools (git_commit_tool, git_checkout_tool, git_create_branch_tool).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_add_tool Rate-limited

git_add_tool 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_tool": {
      "limits": [
        {
          "counter": "git_add_tool_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 MCP Git Commit Generator, so you can run agents against it safely.

FAQ

Questions about git_add_tool

What does the git_add_tool tool do? +

git_add_tool. It is categorised as a Write tool in the MCP Git Commit Generator 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_tool? +

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

What risk level is git_add_tool? +

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

Can I rate-limit git_add_tool? +

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

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

git_add_tool is provided by the MCP Git Commit Generator MCP server (luicciandev/mcp_git_commit_generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.