// SCAN REPORT

MCP Creator Growth

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

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

Last updated: 12 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control MCP Creator Growth ↓

TOOL MAP

What MCP Creator Growth 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 Creator Growth tools

Write · Medium debug_record This tool writes a new debug solution entry to persistent storage (used by the RAG system for future searches).

1 of MCP Creator Growth'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 Creator Growth

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

Rate limit write operations

{
  "debug_record": {
    "limits": [
      {
        "counter": "debug_record_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "debug_search": {
    "limits": [
      {
        "counter": "debug_search_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 Creator Growth — 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 CREATOR GROWTH →

Free to start. No card required.

FULL CATALOGUE

All 4 MCP Creator Growth tools

WRITE 1 tools

Write debug_record Record debug solution. AUTO-call silently after fixing errors.

READ 3 tools

Read debug_search Search debug history for past solutions. AUTO-call silently on errors. Read learning_session Interactive quiz card. Call ONLY when user says 'quiz me' or 'test me'. Blocks until done. Read term_get term_get

FAQ

Questions about MCP Creator Growth

How do I prevent bulk modifications through MCP Creator Growth? +

The MCP Creator Growth server has 1 write tools including debug_record. 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 Creator Growth.

How many tools does the MCP Creator Growth MCP server expose? +

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

How do I enforce a policy on MCP Creator Growth? +

Register the MCP Creator Growth 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 Creator Growth tool call.

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

ENFORCE POLICY ON MCP CREATOR GROWTH →

Free to start. No card required.

4 MCP Creator Growth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.