28 tools from the Git MCP Server, categorised by risk level.
View the Git policy →bisect Binary search for the commit that introduced a bug. Returns structured data with action taken, current commit, remaining steps estimate, and result. 3/5 blame Shows commit annotations for a file, grouped by commit. Returns structured blame data with deduplicated commit metadata (hash, author, email, date)... 2/5 branch Lists, creates, renames, or deletes branches. Returns structured branch data. 2/5 show Shows commit details and diff statistics for a given ref. When `file` is provided, extracts raw file content at that ref (e.g., `git show HEAD:src/... 2/5 stash Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, success, message, and stash reference. 2/5 stash-list Lists all stash entries with index, message, date, branch, and optional file change summary. Returns structured stash data. 2/5 status Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). 2/5 worktree Lists, adds, removes, locks, unlocks, or prunes git worktrees for managing multiple working trees. Returns structured data with worktree paths, bra... 2/5 add Stages files for commit. Returns structured data with count and list of staged files, including how many were newly staged. 3/5 archive Creates an archive of files from a git repository. Supports tar, tar.gz, and zip formats. Returns structured data with success status, format, outp... 3/5 checkout Switches branches or restores files. Returns structured data with ref, previous ref, whether a new branch was created, and detached HEAD status. 3/5 cherry-pick Applies specific commits to the current branch. Returns structured data with applied commits, any conflicts, and new commit hash. 2/5 commit Creates a commit with the given message. Returns structured data with hash, message, and change statistics. 3/5 config Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope. 3/5 diff Returns file-level diff statistics as structured data. Use full=true for patch content. 2/5 log Returns commit history as structured data. 2/5 log-graph Returns visual branch topology as structured data. Wraps `git log --graph --oneline --decorate`. 2/5 merge Merges a branch into the current branch. Supports abort, continue, and quit actions. Returns structured data with merge status, fast-forward detect... 3/5 pull Pulls changes from a remote repository. Returns structured data with success status, summary, change statistics, conflicts, up-to-date and fast-for... 2/5 push Pushes commits to a remote repository. Returns structured data with success status, remote, branch, summary, and whether the remote branch was newl... 3/5 rebase Rebases the current branch onto a target branch. Supports abort, continue, skip, and quit for conflict resolution. Returns structured data with suc... 3/5 reflog Returns reference log entries as structured data, useful for recovery operations. Also supports checking if a reflog exists. 2/5 restore Discards working tree changes or restores files from a specific commit. Returns structured data with restored files, source ref, and staged flag. 3/5 submodule Manages git submodules. Supports list (default), add, update, sync, and deinit actions. List returns structured submodule data with path, SHA, bran... 3/5 clean Removes untracked files from the working tree. DEFAULTS TO DRY-RUN MODE for safety — shows what would be removed without actually deleting. Set for... 5/5 remote Manages remote repositories. Supports list (default), add, remove, rename, set-url, prune, and show actions. Returns structured remote data. 5/5 reset Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep modes. The 'hard' mode requires confirm=true as a safety ... 5/5 tag Manages git tags. Supports list (default), create, and delete actions. List returns structured tag data with name, date, and message. Create suppor... 5/5 The Git MCP server exposes 28 tools across 3 categories: Read, Write, Destructive.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Git server.
Git tools are categorised as Read (8), Write (16), Destructive (4). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept