git_add · Context MCP: Risk & Policy

WHAT IT DOES

What git_add does on Context

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

WHY IT NEEDS A POLICY

Why git_add needs a policy

git_add stages changes for later commit but does not irreversibly delete data (would be Destructive) or execute arbitrary code (would be Execute). It's a Write operation because it modifies the repository state reversibly. The medium severity reflects that misuse could stage unintended files, potentially exposing secrets or committing unwanted changes—but the effects are recoverable.

From the tool's definition Tool name 'git_add' and description 'Stage files for commit' indicate the tool modifies Git's index/staging area, which is a reversible write operation (staging can be undone with git reset).

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

FAQ

Questions about git_add

What does the git_add tool do? +

Stage files for commit. Pass paths:[. It is categorised as a Write tool in the Context 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 Context 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 Context. 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 Context MCP server (vibhasdutta/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.