AI agents call book_search 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.
The tool name 'book_search' most naturally maps to a search operation that retrieves data without modifying state. Given the context of Legado's book management API and the pattern of sibling read operations, this is classified as Read. The empty description reduces confidence slightly, but the semantic meaning of 'search' and consistency with the tool ecosystem support the Read categorization.
From the tool's definition Tool name is 'book_search' which implies querying or retrieving book information. The empty description is uninformative, but the naming convention combined with sibling tools (book_get_chapters, book_get_content, book_get_cover) that clearly perform…
Documented attack patterns abuse exactly the kind of access book_search gives an agent:
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_search:
{
"version": "1",
"default": "deny",
"tools": {
"book_search": {}
}
}book_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
book_search. It is categorised as a Read tool in the Legado MCP Server, which means it retrieves data without modifying state.
Register the Legado MCP server in PolicyLayer and add a rule for book_search: 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.
book_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the book_search 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.
Set action: deny in the PolicyLayer policy for book_search. 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.
book_search 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.
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.