deep_search_book

Search for a query directly inside a specific book by converting it to text on-the-fly. Useful for books not yet indexed by Calibre FTS.

SERVERCalibre SOURCE2b3pro/calibre-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/2b3pro-calibre-mcp/deep-search-book.md

WHAT IT DOES

What deep_search_book does on Calibre

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

RISK

Why deep_search_book is rated Low

This tool performs a read-only search operation within book content. While it converts books to text on-the-fly, this is a transient operation for searching purposes only—no data is created, modified, deleted, or executed. The blast radius if misused is minimal: an agent could only retrieve or discover information from existing ebook content, not alter it or trigger external actions.

From the tool's definition Tool description states it 'Search[es] for a query directly inside a specific book' and is 'Useful for books not yet indexed by Calibre FTS.' The verb 'search' combined with conversion to text for querying indicates pure information retrieval with no…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deep_search_book safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Calibre, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deep_search_book, this is the rule to start with:

deep_search_book Allowed

deep_search_book is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deep_search_book": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Calibre, apply this rule, and every deep_search_book call is checked against it from then on.

FAQ

Questions about deep_search_book

What does the deep_search_book tool do? +

Search for a query directly inside a specific book by converting it to text on-the-fly. Useful for books not yet indexed by Calibre FTS. It is categorised as a Read tool in the Calibre MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on deep_search_book? +

Register the Calibre MCP server in PolicyLayer and add a rule for deep_search_book: 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 Calibre. Nothing to install.

What risk level is deep_search_book? +

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

Can I rate-limit deep_search_book? +

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

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

deep_search_book is provided by the Calibre MCP server (2b3pro/calibre-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Calibre, and thousands of servers like it.

This server

All 10 Calibre tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →