// SCAN REPORT

GitHubMcpServer

5 tools. 2 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 03/07/2026

How to control GitHubMcpServer ↓

TOOL MAP

What GitHubMcpServer exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous GitHubMcpServer tools

Write · High createRepository This tool creates a new repository, which is a reversible write operation. Write · Medium updateRepo Based on the tool name and context (GitHub repository management server where 'update' operations modify existing resources), this tool creates or modifies data reversibly, fitting the Write category.

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

POLICY

How to control GitHubMcpServer

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

Rate limit write operations

{
  "createRepository": {
    "limits": [
      {
        "counter": "createrepository_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "geAllUserRepo": {
    "limits": [
      {
        "counter": "gealluserrepo_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 GitHubMcpServer — 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 GITHUBMCPSERVER →

Instant setup, no code required.

FULL CATALOGUE

All 5 GitHubMcpServer tools

WRITE 2 tools

Write createRepository createRepository Write updateRepo updateRepo

READ 3 tools

Read geAllUserRepo geAllUserRepo Read getRepoActivity getRepoActivity Read getUserRepo getUserRepo

FAQ

Questions about GitHubMcpServer

How do I prevent bulk modifications through GitHubMcpServer? +

The GitHubMcpServer server has 2 write tools including createRepository, updateRepo. 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 GitHubMcpServer.

How many tools does the GitHubMcpServer MCP server expose? +

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

How do I enforce a policy on GitHubMcpServer? +

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

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

ENFORCE POLICY ON GITHUBMCPSERVER →

Instant setup, no code required.

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