git_context · Git MCP: Risk & Policy

WHAT IT DOES

What git_context does on Git

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

WHY IT NEEDS A POLICY

Why git_context needs a policy

The tool supports multiple actions including read-only ones (summary, search, get_config, aliases) but also 'set_config' which modifies repository configuration. Under the most-severe-applicable rule, the presence of set_config elevates this to Write. Misconfiguring git settings could affect remote URLs, user identity, hooks, etc., giving it medium severity.

From the tool's definition 'set_config' action listed explicitly — 'Use action=summary|search|get_config|set_config|aliases for repo context operations'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_context Rate-limited

git_context 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_context": {
      "limits": [
        {
          "counter": "git_context_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 Git, so you can run agents against it safely.

FAQ

Questions about git_context

What does the git_context tool do? +

Context/config tool. Use action=summary|search|get_config|set_config|aliases for repo context operations. It is categorised as a Write tool in the Git 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_context? +

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

What risk level is git_context? +

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

Can I rate-limit git_context? +

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

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

git_context is provided by the Git MCP server (selfagency/git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.