// SCAN REPORT

Wellread

3 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

2 read-only

3 tools total

Community server · catalogue entry verified 12/06/2026

How to control Wellread ↓

TOOL MAP

What Wellread exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Wellread tools

Write · Medium save This tool creates and persists data to a shared research cache accessible by multiple AI agents and users globally.

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

POLICY

How to control Wellread

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

Rate limit write operations

{
  "save": {
    "limits": [
      {
        "counter": "save_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "search": {
    "limits": [
      {
        "counter": "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 Wellread — 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 WELLREAD →

Free to start. No card required.

FULL CATALOGUE

All 3 Wellread tools

WRITE 1 tools

Write save Save research to collective memory. Call directly BEFORE responding to the user, after any live research (web

READ 2 tools

Read search Search collective research memory. Call FIRST and ALONE (no parallel tools) before any web search or implement Read stats View your personal wellread stats: karma, savings, contributions, and network impact.

FAQ

Questions about Wellread

How do I prevent bulk modifications through Wellread? +

The Wellread server has 1 write tools including save. 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 Wellread.

How many tools does the Wellread MCP server expose? +

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

How do I enforce a policy on Wellread? +

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

Deterministic rules across all 3 Wellread tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WELLREAD →

Free to start. No card required.

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