Cancel any ERPNext submitted document (changes status to Cancelled). Applies to submittable DocTypes like Sales Order, Purchase Order, Sales Invoice, etc. Calls frappe.client.cancel via the Frappe method API.
Part of the Mcp Erpnext server.
Free to start. No card required.
AI agents may call erpnext_doc_cancel 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. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call erpnext_doc_cancel in a loop, permanently destroying resources in Mcp Erpnext. There is no undo for destructive operations. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"erpnext_doc_cancel"
]
}See the full Mcp Erpnext policy for all 120 tools.
These attack patterns abuse exactly the kind of access erpnext_doc_cancel gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Cancel any ERPNext submitted document (changes status to Cancelled). Applies to submittable DocTypes like Sales Order, Purchase Order, Sales Invoice, etc. Calls frappe.client.cancel via the Frappe method API.. 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.
Register the Mcp Erpnext MCP server in PolicyLayer and add a rule for erpnext_doc_cancel: 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 Mcp Erpnext. Nothing to install.
erpnext_doc_cancel 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 erpnext_doc_cancel 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 erpnext_doc_cancel. 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.
erpnext_doc_cancel is provided by the Mcp Erpnext MCP server (@casys/mcp-erpnext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Mcp Erpnext tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.