// SCAN REPORT

Git

14 tools. 7 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 5 Apr 2026

7 can modify or destroy data

7 read-only

14 tools total

// TOOL MAP

Read (7) Write / Execute (6) Destructive / Financial (1)

// WHAT CAN GO WRONG

Destructive tools (git_reset) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (git_add, git_checkout, git_clone) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

One command. Full control.

Intercept sits between your agent and Git. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @modelcontextprotocol/server-git

Scans every tool. Generates a policy. Starts enforcing.

Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client

// RECOMMENDED RULES

Deny destructive operations

git_reset:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

git_add:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

git_branch:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 14 GIT TOOLS

DESTRUCTIVE 1 tools

Destructive git_reset

WRITE 6 tools

Write git_add Write git_checkout Write git_clone Write git_commit Write git_create_branch Write git_init

READ 7 tools

Read git_branch Read git_diff Read git_diff_staged Read git_diff_unstaged Read git_log Read git_show Read git_status

// FAQ

Can an AI agent delete data through the Git MCP server? +

Yes. The Git server exposes 1 destructive tools including git_reset. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Git? +

The Git server has 6 write tools including git_add, git_checkout, git_clone. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Git MCP server expose? +

14 tools across 3 categories: Destructive, Read, Write. 7 are read-only. 7 can modify, create, or delete data.

How do I add Intercept to my Git setup? +

One line change. Instead of running the Git server directly, prefix it with Intercept: intercept -c git.yaml -- npx -y @@modelcontextprotocol/server-git. Download a pre-built policy from policylayer.com/policies/git and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init

Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.

Git

One command. Full control.

Other MCP servers with similar tools.

Control every MCP tool call your agent makes.

Control every MCP tool call
your agent makes.