Legado

31 tools. 16 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

16 can modify or destroy data
15 read-only
31 tools total

Community server · catalogue entry verified 12/06/2026

How to control Legado ↓

What Legado exposes to your agents

Read (15) Write / Execute (12) Destructive / Financial (4)
Critical Risk

The most dangerous Legado tools

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

How to control Legado

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

Deny destructive operations
{
  "book_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "web_read_config_save": {
    "limits": [
      {
        "counter": "web_read_config_save_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "book_get_chapters": {
    "limits": [
      {
        "counter": "book_get_chapters_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Legado — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LEGADO →

Free to start. No card required.

All 31 Legado tools

Related servers

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

Questions about Legado

Can an AI agent delete data through the Legado MCP server? +

Yes. The Legado server exposes 4 destructive tools including book_delete, book_source_delete_many, rss_source_delete_many. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Legado? +

The Legado server has 9 write tools including web_read_config_save, book_add_local, book_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 Legado.

How many tools does the Legado MCP server expose? +

31 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Legado? +

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

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.