// SCAN REPORT

MCP Everything

7 tools. 6 can modify or destroy data without limits.

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

Last updated: 5 Jul 2026

6 can modify or destroy data

1 read-only

7 tools total

Community server · catalogue entry verified 05/07/2026

How to control MCP Everything ↓

TOOL MAP

What MCP Everything exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Everything tools

Execute · Medium long_running_operation The name implies executing a long-running operation, which typically falls under Execute category. Write · Medium add add Write · Medium print_env print_env Write · Medium sample_llm sample_llm

6 of MCP Everything's 7 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 Everything

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

Rate limit write operations

{
  "add": {
    "limits": [
      {
        "counter": "add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_tiny_image": {
    "limits": [
      {
        "counter": "get_tiny_image_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 Everything — 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 EVERYTHING →

Instant setup, no code required.

FULL CATALOGUE

All 7 MCP Everything tools

EXECUTE 1 tools

Execute long_running_operation long_running_operation

WRITE 3 tools

Write add add Write print_env print_env Write sample_llm sample_llm

READ 1 tools

Read get_tiny_image get_tiny_image

OTHER 2 tools

Other annotated_message annotated_message Other echo echo

FAQ

Questions about MCP Everything

How do I prevent bulk modifications through MCP Everything? +

The MCP Everything server has 3 write tools including add, print_env, sample_llm. 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 Everything.

How many tools does the MCP Everything MCP server expose? +

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

How do I enforce a policy on MCP Everything? +

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

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

ENFORCE POLICY ON MCP EVERYTHING →

Instant setup, no code required.

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