Permanently delete a document from ERPNext. This action cannot be undone. Submitted documents must be cancelled before deletion.
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 irreversibly removes data from the system with no recovery mechanism. In an ERP system, documents represent critical business records (invoices, orders, employee records, etc.). Unauthorized or mistaken deletion could destroy essential business data.
From the tool's definition Tool name is 'delete_document' and description explicitly states 'Permanently delete a document from ERPNext. This action cannot be undone.' The use of 'Permanently' and 'cannot be undone' are clear indicators of irreversible data loss.
Documented attack patterns abuse exactly the kind of access delete_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ERPNext MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_document:
{
"version": "1",
"default": "deny",
"hide": [
"delete_document"
]
}delete_document disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete a document from ERPNext. This action cannot be undone. Submitted documents must be cancelled before deletion. 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 (rakeshgangwar/erpnext-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 ERPNext MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 ERPNext MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.