Delete a book from the library by ID
AI agents call delete_book to permanently remove resources in OpenAPI REST MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a book record) from the library system with no option to undo the operation. Deletion is irreversible and constitutes the most severe category (Destructive) per the classification hierarchy. High severity reflects the risk that an AI agent could inadvertently destroy library records if misdirected or given incorrect book IDs.
From the tool's definition Tool name is 'delete_book' with description 'Delete a book from the library by ID'. The verb 'Delete' is explicit and irreversible.
Attacks that exploit this kind of access
Delete a book from the library by ID. It is categorised as a Destructive tool in the OpenAPI REST MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenAPI REST 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 OpenAPI REST 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 OpenAPI REST MCP Server MCP server (saranazeer27/mcp). 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 →