// SCAN REPORT

Github

6 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

4 can modify or destroy data

2 read-only

6 tools total

Community server · catalogue entry verified 03/07/2026

How to control Github ↓

TOOL MAP

What Github exposes to your agents

Read (2) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Github tools

Write · Low github_create_feature_branch Creating a feature branch is a write operation that modifies repository state by introducing a new branch reference. Write · Medium github_create_pull_request Creating a pull request is a Write action: it creates new repository state (the PR object, associated metadata, triggers CI/CD pipelines, and notifies reviewers) but is fully reversible (PRs can be closed without merging Write · Medium github_prepare_feature_workflow This tool performs reversible data modification (branch creation and main updates) but does not push changes to remote, delete data, or trigger external deployments. Write · Medium github_push_feature_branch This tool writes to a Git repository by pushing local commits to a remote feature branch and configuring upstream tracking.

4 of Github's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Github

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

Rate limit write operations

{
  "github_create_feature_branch": {
    "limits": [
      {
        "counter": "github_create_feature_branch_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "github_pull_main": {
    "limits": [
      {
        "counter": "github_pull_main_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 Github — 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 GITHUB →

Instant setup, no code required.

FULL CATALOGUE

All 6 Github tools

WRITE 4 tools

Write github_create_feature_branch Create a new feature branch from the base branch after validating safety constraints. Write github_create_pull_request Create a ready-for-review pull request from a pushed feature branch into the base branch. Write github_prepare_feature_workflow Check status, update main, and create a new feature branch. Does not push or create a PR. Write github_push_feature_branch Push a non-protected feature branch and set upstream. Refuses main/master.

READ 2 tools

Read github_pull_main Fetch, switch to the base branch, and fast-forward pull from the configured remote. Read github_repo_status Inspect a local Git repository status, branch, remotes, upstream, and MCP allowed roots.

FAQ

Questions about Github

How do I prevent bulk modifications through Github? +

The Github server has 4 write tools including github_create_feature_branch, github_create_pull_request, github_prepare_feature_workflow. 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 Github.

How many tools does the Github MCP server expose? +

6 tools across 2 categories: Read, Write. 2 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Github? +

Register the Github 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 Github tool call.

Deterministic rules across all 6 Github tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GITHUB →

Instant setup, no code required.

6 Github tools catalogued and risk-classified — across an index of 43,000+ MCP servers.