Delete an image from the gallery
AI agents call delete_image to permanently remove resources in BookStack 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 an image resource from the system without the ability to undo the action. While the blast radius is limited to a single image (not a cascading deletion like delete_book), the irreversible nature of deletion and the presence of sibling destructive tools (delete_book, delete_chapter, delete_page) confirm the Destructive category.
From the tool's definition Tool name: 'delete_image'; description: 'Delete an image from the gallery'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an image from the gallery. It is categorised as a Destructive tool in the BookStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for delete_image: 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 BookStack MCP Server. Nothing to install.
delete_image 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_image 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_image. 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_image is provided by the BookStack MCP Server MCP server (lautarobarba/bookstack_mcp_server). 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 →