// SCAN REPORT

GitHub Repository Analyzer

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

1 write tool that can modify data. Rate limits recommended.

Last updated: 5 Jul 2026

1 can modify or destroy data

4 read-only

5 tools total

Community server · catalogue entry verified 05/07/2026

How to control GitHub Repository Analyzer ↓

TOOL MAP

What GitHub Repository Analyzer exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous GitHub Repository Analyzer tools

Write · Low generate_activity_chart This tool creates/generates a new visualization artifact (a chart), which constitutes a Write operation.

1 of GitHub Repository Analyzer'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 GitHub Repository Analyzer

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

Rate limit write operations

{
  "generate_activity_chart": {
    "limits": [
      {
        "counter": "generate_activity_chart_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_activity_metrics": {
    "limits": [
      {
        "counter": "get_activity_metrics_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 Repository Analyzer — 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 REPOSITORY ANALYZER →

Instant setup, no code required.

FULL CATALOGUE

All 5 GitHub Repository Analyzer tools

WRITE 1 tools

Write generate_activity_chart Create a visual chart of repository commit activity.

READ 4 tools

Read get_activity_metrics Calculate repository activity metrics. Read get_commit_history Analyze recent code changes in a repository. Read get_repository_info Retrieve basic metadata about a GitHub repository. Read get_repository_issues List and categorize repository issues.

FAQ

Questions about GitHub Repository Analyzer

How do I prevent bulk modifications through GitHub Repository Analyzer? +

The GitHub Repository Analyzer server has 1 write tools including generate_activity_chart. 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 Repository Analyzer.

How many tools does the GitHub Repository Analyzer MCP server expose? +

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

How do I enforce a policy on GitHub Repository Analyzer? +

Register the GitHub Repository Analyzer 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 Repository Analyzer tool call.

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

ENFORCE POLICY ON GITHUB REPOSITORY ANALYZER →

Instant setup, no code required.

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