Delete a generated document
AI agents call delete_document to permanently remove resources in docxtpl 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 documents without recovery options, fitting the Destructive category. The severity is high because loss of generated documents could impact workflow and compliance (especially for templates used in regulated environments).
From the tool's definition Tool name is 'delete_document' with description 'Delete a generated document'. The verb 'delete' combined with document removal indicates irreversible destruction of data.
Attacks that exploit this kind of access
Delete a generated document. It is categorised as a Destructive tool in the docxtpl MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the docxtpl 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 docxtpl 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 docxtpl MCP Server MCP server (z1w2r3/doc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_document is one line of docxtpl MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →