// SCAN REPORT

Server Github

26 tools. 12 can modify or destroy data without limits.

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

Last updated: 5 Jul 2026

12 can modify or destroy data

14 read-only

26 tools total

Verified server · catalogue entry verified 05/07/2026 · full schemas captured for 26 of 26 tools

How to control Server Github ↓

TOOL MAP

What Server Github exposes to your agents

Read (14) Write / Execute (12) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Server Github costs in tokens

3,553 tokens of tool definitions, loaded on every request

1.8% of a 200k context window

360 heaviest tool: create_pull_request_review

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Server Github tools

Write · High create_or_update_file This tool creates new files or modifies existing ones in a GitHub repository, which are reversible write operations. Write · High push_files The tool creates or modifies data in a repository reversibly (commits can be reverted, files can be edited). Write · Medium add_issue_comment This tool creates or appends data to an existing issue in a reversible manner. Write · Medium create_branch Creating a branch is a reversible modification operation—branches can be deleted and the repository state restored.

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

POLICY

How to control Server Github

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

Rate limit write operations

{
  "add_issue_comment": {
    "limits": [
      {
        "counter": "add_issue_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_file_contents": {
    "limits": [
      {
        "counter": "get_file_contents_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 Server 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 SERVER GITHUB →

Instant setup, no code required.

FULL CATALOGUE

All 26 Server Github tools

WRITE 12 tools

Write add_issue_comment Add a comment to an existing issue Write create_branch Create a new branch in a GitHub repository Write create_issue Create a new issue in a GitHub repository Write create_or_update_file Create or update a single file in a GitHub repository Write create_pull_request Create a new pull request in a GitHub repository Write create_pull_request_review Create a review on a pull request Write create_repository Create a new GitHub repository in your account Write fork_repository Fork a GitHub repository to your account or specified organization Write merge_pull_request Merge a pull request Write push_files Push multiple files to a GitHub repository in a single commit Write update_issue Update an existing issue in a GitHub repository Write update_pull_request_branch Update a pull request branch with the latest changes from the base branch

READ 14 tools

Read get_file_contents Get the contents of a file or directory from a GitHub repository Read get_issue Get details of a specific issue in a GitHub repository. Read get_pull_request Get details of a specific pull request Read get_pull_request_comments Get the review comments on a pull request Read get_pull_request_files Get the list of files changed in a pull request Read get_pull_request_reviews Get the reviews on a pull request Read get_pull_request_status Get the combined status of all status checks for a pull request Read list_commits Get list of commits of a branch in a GitHub repository Read list_issues List issues in a GitHub repository with filtering options Read list_pull_requests List and filter repository pull requests Read search_code Search for code across GitHub repositories Read search_issues Search for issues and pull requests across GitHub repositories Read search_repositories Search for GitHub repositories Read search_users Search for users on GitHub

FAQ

Questions about Server Github

How do I prevent bulk modifications through Server Github? +

The Server Github server has 12 write tools including add_issue_comment, create_branch, create_issue. 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 Server Github.

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

26 tools across 2 categories: Read, Write. 14 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Server Github? +

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

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

ENFORCE POLICY ON SERVER GITHUB →

Instant setup, no code required.

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