// SCAN REPORT

MCP Merge Request Summarizer

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

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

Last updated: 1 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 01/07/2026

How to control MCP Merge Request Summarizer ↓

TOOL MAP

What MCP Merge Request Summarizer exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Merge Request Summarizer tools

Write · Medium set_working_directory This tool modifies the operational context of the server by setting a working directory.

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

POLICY

How to control MCP Merge Request Summarizer

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

Rate limit write operations

{
  "set_working_directory": {
    "limits": [
      {
        "counter": "set_working_directory_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_git_commits": {
    "limits": [
      {
        "counter": "analyze_git_commits_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 MCP Merge Request Summarizer — 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 MCP MERGE REQUEST SUMMARIZER →

Instant setup, no code required.

FULL CATALOGUE

All 4 MCP Merge Request Summarizer tools

WRITE 1 tools

Write set_working_directory Set the working directory context for the MCP server.

READ 3 tools

Read analyze_git_commits Analyze git commits and categorize them by type Read generate_merge_request_summary Generate a comprehensive merge request summary from git logs Read get_working_directory Get the current working directory context.

FAQ

Questions about MCP Merge Request Summarizer

How do I prevent bulk modifications through MCP Merge Request Summarizer? +

The MCP Merge Request Summarizer server has 1 write tools including set_working_directory. 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 MCP Merge Request Summarizer.

How many tools does the MCP Merge Request Summarizer MCP server expose? +

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

How do I enforce a policy on MCP Merge Request Summarizer? +

Register the MCP Merge Request Summarizer 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 MCP Merge Request Summarizer tool call.

Deterministic rules across all 4 MCP Merge Request Summarizer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP MERGE REQUEST SUMMARIZER →

Instant setup, no code required.

4 MCP Merge Request Summarizer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.