git_commit · Context MCP: Risk & Policy

WHAT IT DOES

What git_commit does on Context

AI agents use git_commit 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_commit needs a policy

git_commit creates a new commit object in the repository, modifying the git history and refs. While git commits are technically recoverable via git reflog, they are persistent modifications to the repository state and cannot be undone without additional git operations.

From the tool's definition Tool description states 'Commit staged changes' and 'auto-stage tracked modified files', which are write operations that modify the git repository state irreversibly at the commit level, though the actual file content may be recoverable via git history.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_commit Rate-limited

git_commit 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_commit": {
      "limits": [
        {
          "counter": "git_commit_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_commit

What does the git_commit tool do? +

Commit staged changes. Set all:true to auto-stage tracked modified files first. Auto-saves context entry. 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_commit? +

Register the Context MCP server in PolicyLayer and add a rule for git_commit: 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_commit? +

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

Can I rate-limit git_commit? +

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

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

git_commit 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.