// SCAN REPORT

Git MCP Server

32 tools. 21 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

21 can modify or destroy data

11 read-only

32 tools total

Community server · catalogue entry verified 30/06/2026

How to control Git MCP Server ↓

TOOL MAP

What Git MCP Server exposes to your agents

Read (11) Write / Execute (17) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Git MCP Server tools

Destructive · High git_branch_delete This tool irreversibly deletes git branches, which cannot be undone without access to reflog or backups. Destructive · High git_clean The git_clean command irreversibly deletes untracked files from the working directory with no undo mechanism. Destructive · High git_reset_commit git_reset_commit can irreversibly discard uncommitted changes in the working directory when used with hard mode. Destructive · Medium git_stash_pop git_stash_pop irreversibly removes the stash entry from the stash stack.

21 of Git MCP Server's 32 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Git MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "git_branch_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

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

Rate limit write operations

{
  "git_add": {
    "limits": [
      {
        "counter": "git_add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "git_branch_list": {
    "limits": [
      {
        "counter": "git_branch_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register Git MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GIT →

Instant setup, no code required.

FULL CATALOGUE

All 32 Git MCP Server tools

DESTRUCTIVE 4 tools

Destructive git_branch_delete Delete a branch. Removes the specified branch from the repository. By default, only fully merged branches can Destructive git_clean Remove untracked files from the working directory. Deletes files that aren Destructive git_reset_commit Reset the current branch to a specific commit. This changes where the branch HEAD points to, with different mo Destructive git_stash_pop Apply and remove a stash. Applies the specified stash to the working directory and then removes it from the st

EXECUTE 2 tools

Execute git_checkout Checkout a branch, tag, or commit. Switches the working directory to the specified target and updates HEAD to Execute git_rebase Reapply commits on top of another base commit. Takes all changes that were committed on one branch and replays

WRITE 15 tools

Write git_add Stage files for commit. Adds file contents to the index (staging area) in preparation for the next commit. Can Write git_branch_create Create a new branch. Creates a new branch at the specified reference point (commit or branch) and optionally c Write git_cherry_pick Apply changes from specific commits to the current branch. Takes the changes introduced in one or more existin Write git_clear_working_dir Clear the global working directory setting. Tools will use their explicitly provided path parameters. Write git_clone Clone a Git repository. Downloads a repository from a remote location and creates a local copy with all its hi Write git_commit Commit staged changes to the repository. Creates a new commit containing the current contents of the index wit Write git_init Initialize a new Git repository. Creates the necessary directory structure and Git metadata for a new Git repo Write git_merge Merge a branch into the current branch. Combines changes from the specified branch into the current branch wit Write git_push Push local changes to a remote repository. Uploads local branch commits to the remote repository, updating rem Write git_remote_add Add a new remote repository reference. Creates a connection to a remote repository with a name and URL, allowi Write git_reset Unstage files from the index. Removes file contents from the staging area while preserving the working directo Write git_set_working_dir Set a global working directory path for all Git operations. Future tool calls can use Write git_stash_apply Apply stashed changes to the working directory. Applies changes from the specified stash to the current workin Write git_stash_create Save uncommitted changes to a stash. Captures the current state of working directory and index and saves it on Write git_tag_create Create a new tag in the repository. Tags are references that point to specific commits, useful for marking rel

READ 11 tools

Read git_branch_list List branches in a repository. Displays both local and optionally remote branches, clearly marking the current Read git_diff_staged Show staged changes ready for commit. Displays the differences between the index (staging area) and the latest Read git_diff_unstaged Show unstaged changes in the working directory. Displays the differences between the working directory and the Read git_fetch Fetch changes from a remote repository. Downloads objects and refs from a remote repository without merging th Read git_log Show commit history. Displays a log of commits in reverse chronological order, optionally limited to a specifi Read git_pull Pull changes from a remote repository. Fetches from a remote repository and integrates changes into the curren Read git_remote_list List all configured remote repositories. Displays the names and URLs of all remotes associated with the reposi Read git_show Show details of a specific commit. Displays the commit message, author, date, and the changes introduced by th Read git_stash_list List all stashes in the repository. Shows the stack of stashes that have been created and their descriptions, Read git_status Get repository status. Shows the working tree status including tracked/untracked files, modifications, staged Read git_tag_list List all tags in the repository. Displays all tag names that exist in the repository, which can be used to ide

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Git MCP Server

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

Yes. The Git MCP Server server exposes 4 destructive tools including git_branch_delete, git_clean, git_reset_commit. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Git MCP Server? +

The Git MCP Server server has 15 write tools including git_add, git_branch_create, git_cherry_pick. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Git MCP Server.

How many tools does the Git MCP Server MCP server expose? +

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

How do I enforce a policy on Git MCP Server? +

Register the Git MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Git MCP Server tool call.

Deterministic rules across all 32 Git MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GIT →

Instant setup, no code required.

32 Git MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.