Removes a book from the library.
AI agents call delete_book to permanently remove resources in Personal Library MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a book record from persistent storage with no stated undo capability. This is a destructive operation that cannot be reversed, placing it in the Destructive category. Severity is high because deletion of user library data could result in loss of reading history, notes, or curated collections, though the blast radius is limited to personal library scope rather than critical system data.
From the tool's definition Tool name 'delete_book' and description 'Removes a book from the library' indicate irreversible deletion of data from the SQLite database.
Attacks that exploit this kind of access
Removes a book from the library. It is categorised as a Destructive tool in the Personal Library MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Personal Library MCP Server MCP server in PolicyLayer and add a rule for delete_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 Personal Library MCP Server. Nothing to install.
delete_book 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 delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_book is provided by the Personal Library MCP Server MCP server (srgsanky/mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →