// MCP TOOL REFERENCE

GITHUB TOOLS

28 tools from the Github MCP Server, categorised by risk level.

// ALL 28 GITHUB TOOLS

READ 8 tools

Read bisect Binary search for the commit that introduced a bug. Returns structured data with action taken, current comm... Read blame Shows commit annotations for a file, grouped by commit. Returns structured blame data with deduplicated com... Read branch Lists, creates, renames, or deletes branches. Returns structured branch data. Pass `path` to target a speci... Read show Shows commit details and diff statistics for a given ref. When `file` is provided, extracts raw file conten... Read stash Pushes, pops, applies, drops, shows, or clears stash entries. Returns structured result with action, succes... Read stash-list Lists all stash entries with index, message, date, branch, and optional file change summary. Returns struct... Read status Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). Read worktree Lists, adds, removes, locks, unlocks, or prunes git worktrees for managing multiple working trees. Returns ...

WRITE 16 tools

Write add Stages files for commit. Returns structured data with count and list of staged files, including how many we... Write archive Creates an archive of files from a git repository. Supports tar, tar.gz, and zip formats. Returns structure... Write checkout Switches branches or restores files. Returns structured data with ref, previous ref, whether a new branch w... Write cherry-pick Applies specific commits to the current branch. Returns structured data with applied commits, any conflicts... Write commit Creates a commit with the given message. Returns structured data with hash, message, and change statistics.... Write config Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, sy... Write diff Returns file-level diff statistics as structured data. Use full=true for patch content. Write log Returns commit history as structured data. Write log-graph Returns visual branch topology as structured data. Wraps `git log --graph --oneline --decorate`. Write merge Merges a branch into the current branch. Supports abort, continue, and quit actions. Returns structured dat... Write pull Pulls changes from a remote repository. Returns structured data with success status, summary, change statis... Write push Pushes commits to a remote repository. Returns structured data with success status, remote, branch, summary... Write rebase Rebases the current branch onto a target branch. Supports abort, continue, skip, and quit for conflict reso... Write reflog Returns reference log entries as structured data, useful for recovery operations. Also supports checking if... Write restore Discards working tree changes or restores files from a specific commit. Returns structured data with restor... Write submodule Manages git submodules. Supports list (default), add, update, sync, and deinit actions. List returns struct...

DESTRUCTIVE 4 tools

Destructive clean Removes untracked files from the working tree. DEFAULTS TO DRY-RUN MODE for safety — shows what would be re... Destructive remote Manages remote repositories. Supports list (default), add, remove, rename, set-url, prune, and show actions... Destructive reset Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep modes. The 'hard'... Destructive tag Manages git tags. Supports list (default), create, and delete actions. List returns structured tag data wit...

// RUNNING THIS SERVER

The managed route: connect Github through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @paretools/github

// FAQ

How many tools does the Github MCP server have? +

The Github MCP server exposes 28 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Github tools? +

Route the Github server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Github tools fall into? +

Github tools are categorised as Read (8), Write (16), Destructive (4). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.