Critical Risk →

erpnext_doc_delete

Delete any ERPNext document. Only Draft documents can usually be deleted. For submitted documents, use cancel first. Works on any DocType.

Part of the Mcp Erpnext MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@casys/mcp-erpnext Destructive Risk 4/5

AI agents may call erpnext_doc_delete to permanently remove or destroy resources in Mcp Erpnext. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call erpnext_doc_delete in a loop, permanently destroying resources in Mcp Erpnext. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

mcp-erpnext.yaml
tools:
  erpnext_doc_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Erpnext policy for all 120 tools.

Tool Name erpnext_doc_delete
Category Destructive
Risk Level Critical

View all 120 tools →

Agents calling destructive-class tools like erpnext_doc_delete have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

erpnext_doc_delete is one of the critical-risk operations in Mcp Erpnext. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the erpnext_doc_delete tool do? +

Delete any ERPNext document. Only Draft documents can usually be deleted. For submitted documents, use cancel first. Works on any DocType.. It is categorised as a Destructive tool in the Mcp Erpnext MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on erpnext_doc_delete? +

Add a rule in your Intercept YAML policy under the tools section for erpnext_doc_delete. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Erpnext MCP server.

What risk level is erpnext_doc_delete? +

erpnext_doc_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit erpnext_doc_delete? +

Yes. Add a rate_limit block to the erpnext_doc_delete rule in your Intercept 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.

How do I block erpnext_doc_delete completely? +

Set action: deny in the Intercept policy for erpnext_doc_delete. 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.

What MCP server provides erpnext_doc_delete? +

erpnext_doc_delete is provided by the Mcp Erpnext MCP server (@casys/mcp-erpnext). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Erpnext

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.