High Risk →

book_refresh_toc

book_refresh_toc

How to control book_refresh_toc ↓

What book_refresh_toc does on Legado

AI agents invoke book_refresh_toc to trigger actions in Legado. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why book_refresh_toc needs a policy

The name implies triggering a refresh/fetch operation (re-fetching TOC data from a book source), which is an external operation. With no description, confidence is low. Sibling tools like 'book_get_chapters' suggest read operations, but 'refresh' implies actively triggering a network fetch/update rather than a passive read.

From the tool's definition Tool name 'book_refresh_toc' suggests refreshing a table of contents; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access book_refresh_toc gives an agent:

How to control book_refresh_toc

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "book_refresh_toc": {
      "limits": [
        {
          "counter": "book_refresh_toc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

book_refresh_toc stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Legado — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about book_refresh_toc

What does the book_refresh_toc tool do? +

book_refresh_toc. It is categorised as a Execute tool in the Legado MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on book_refresh_toc? +

Register the Legado MCP server in PolicyLayer and add a rule for book_refresh_toc: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Legado. Nothing to install.

What risk level is book_refresh_toc? +

book_refresh_toc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit book_refresh_toc? +

Yes. Add a rate_limit block to the book_refresh_toc rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block book_refresh_toc completely? +

Set action: deny in the PolicyLayer policy for book_refresh_toc. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides book_refresh_toc? +

book_refresh_toc is provided by the Legado MCP server (joestar817/legado-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Legado tool call.

Start from Legado, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

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.