Delete a document.
AI agents call delete_document to permanently remove resources in ERPNext 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 from the ERPNext instance without the ability to recover it. In an ERP system managing documents, inventory, and financial records, unintended deletion could destroy critical business data, accounting records, or inventory transactions. The irreversible nature and potential blast radius across dependent records make this critical severity.
From the tool's definition The tool name is 'delete_document' with description 'Delete a document.' The server description confirms it 'supports full CRUD operations' including deletion. Deletion is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete a document. It is categorised as a Destructive tool in the ERPNext MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ERPNext 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 ERPNext 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 ERPNext MCP Server MCP server (yazelin/erpnext-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 →