Delete document from the Document Storage
AI agents call delete_document to permanently remove resources in PDF Generator API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible delete operation on stored documents. Once executed, the document cannot be recovered through normal means. The blast radius is high because an AI agent with misuse could delete critical business documents, invoices, templates, or workspace data without recourse.
From the tool's definition Tool name is 'delete_document' and description states 'Delete document from the Document Storage' — explicitly describes irreversible removal of data.
Attacks that exploit this kind of access
Delete document from the Document Storage. It is categorised as a Destructive tool in the PDF Generator API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for delete_document: 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 PDF Generator API MCP Server. Nothing to install.
delete_document 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_document 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_document. 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_document is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/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 →