// SCAN REPORT

SEED MCP

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

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

Last updated: 3 Jul 2026

4 can modify or destroy data

8 read-only

12 tools total

Community server · catalogue entry verified 03/07/2026

How to control SEED MCP ↓

TOOL MAP

What SEED MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous SEED MCP tools

Execute · High refresh_seed_membership_site This tool executes a deployment/refresh operation that modifies live infrastructure (the membership site) based on external state (GitHub branch content). Execute · High start_publishing_webserver Starting a web server is an Execute action—it triggers an external operation (server startup) whose effects depend on system configuration and arguments. Write · Medium add_to_seed The tool modifies SEED's internal knowledge/data store by adding to it. Write · High ingest_qa_to_carton The tool ingests and transforms data from one format (GIINT QA) into another (Carton concepts), which constitutes a Write operation — creating or modifying data in the Carton system.

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

POLICY

How to control SEED MCP

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

Rate limit write operations

{
  "add_to_seed": {
    "limits": [
      {
        "counter": "add_to_seed_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_publishing_webserver_status": {
    "limits": [
      {
        "counter": "get_publishing_webserver_status_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 SEED MCP — 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 SEED →

Instant setup, no code required.

FULL CATALOGUE

All 12 SEED MCP tools

EXECUTE 2 tools

Execute refresh_seed_membership_site Trigger a refresh of the SEED membership site from GitHub public branch. Execute start_publishing_webserver start_publishing_webserver

WRITE 2 tools

Write add_to_seed Instructions for extending SEED's knowledge. Write ingest_qa_to_carton Main SEED ingestion function: transforms GIINT QA into Carton concepts.

READ 8 tools

Read get_publishing_webserver_status Check if SEED publishing webserver is running and on what port. Read how_do_i Get help for a specific component. Read list_available_qa_files List available GIINT QA files for ingestion. Read parse_qa_json Parse GIINT QA JSON file into structured IO pairs for ingestion. Read recite_mantra Recite the compound intelligence mantra. Read show_seed_publishing_interface show_seed_publishing_interface Read what_do_i_do Get master instructions for what to do in conversations. Read who_am_i Return unified system identity.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about SEED MCP

How do I prevent bulk modifications through SEED MCP? +

The SEED MCP server has 2 write tools including add_to_seed, ingest_qa_to_carton. 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 SEED MCP.

How many tools does the SEED MCP server expose? +

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

How do I enforce a policy on SEED MCP? +

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

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

ENFORCE POLICY ON SEED →

Instant setup, no code required.

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