config

Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope.

Accepts file system path (path)

Part of the Git MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/git Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use config to create or modify resources in Git. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON CONFIG

Without a policy, an AI agent could call config repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Git.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-dave-london-git.yaml

tools:
  config:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Git policy for all 28 tools.

// DETAILS

Tool Name config

Category Write

MCP Server Git MCP Server

Risk Level Medium

// MORE GIT TOOLS

Destructive clean Destructive remote Destructive reset Destructive tag Write add Write archive Write checkout Write cherry-pick

View all 28 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like config have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the config tool do? +

Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope.. 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 config? +

Add a rule in your Intercept YAML policy under the tools section for config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Git MCP server.

What risk level is config? +

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

Can I rate-limit config? +

Yes. Add a rate_limit block to the config rule in your Intercept 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 config completely? +

Set action: deny in the Intercept policy for config. 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 config? +

config is provided by the Git MCP server (@paretools/git). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

config

Enforce policies on Git