Low Risk

book_get_chapters

book_get_chapters

How to control book_get_chapters ↓

What book_get_chapters does on Legado

AI agents call book_get_chapters to retrieve information from Legado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why book_get_chapters needs a policy

The 'get' prefix and contextual patterns from related tools indicate this retrieves chapter data from books without side effects. Despite the empty description lowering confidence slightly, the consistent naming pattern across the Legado server's Read operations (book_get_*) makes Read the appropriate classification.

From the tool's definition Tool name 'book_get_chapters' indicates data retrieval with 'get' verb. Sibling tools like 'book_get_content', 'book_get_cover', and 'book_get_image' establish a pattern of Read operations on this server.

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

How to control book_get_chapters

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_get_chapters:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "book_get_chapters": {}
  }
}

book_get_chapters is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about book_get_chapters

What does the book_get_chapters tool do? +

book_get_chapters. It is categorised as a Read tool in the Legado MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on book_get_chapters? +

Register the Legado MCP server in PolicyLayer and add a rule for book_get_chapters: 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_get_chapters? +

book_get_chapters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit book_get_chapters? +

Yes. Add a rate_limit block to the book_get_chapters 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_get_chapters completely? +

Set action: deny in the PolicyLayer policy for book_get_chapters. 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_get_chapters? +

book_get_chapters 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.