AI agents call book_delete to permanently remove resources in Legado — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are categorized as Destructive per rules. While description is absent (lowering confidence slightly from 1.0), the tool name and server purpose (management of books in Legado) leave no reasonable interpretation other than permanent removal of book data.
From the tool's definition Tool name 'book_delete' combined with server context enabling management of books in Legado system. Despite empty description, the name unambiguously indicates deletion of book records, which is irreversible.
Documented attack patterns abuse exactly the kind of access book_delete 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_delete:
{
"version": "1",
"default": "deny",
"hide": [
"book_delete"
]
}book_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
book_delete. It is categorised as a Destructive tool in the Legado MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Legado MCP server in PolicyLayer and add a rule for book_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the book_delete 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_delete. 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_delete 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.