AI agents call book_get_content 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 appears designed to fetch or retrieve book content from the Legado Web API. Following the naming convention of other 'book_get_*' sibling tools and the absence of modifying verbs (save, delete, update), this is classified as a Read operation. Severity is low because retrieval operations typically have minimal blast radius unless they expose sensitive data, which is not indicated here.
From the tool's definition Tool name 'book_get_content' indicates retrieval of book content. No description provided, but naming pattern aligns with sibling tools like 'book_get_chapters', 'book_get_cover', 'book_get_image' which are all Read operations.
Documented attack patterns abuse exactly the kind of access book_get_content 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_get_content:
{
"version": "1",
"default": "deny",
"tools": {
"book_get_content": {}
}
}book_get_content 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_get_content. 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_get_content: 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_get_content 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_get_content 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_get_content. 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_get_content 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.