Cancel a submitted document.
AI agents call cancel_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.
Cancelling a submitted document in ERPNext is an irreversible workflow state change — a cancelled document cannot be re-submitted and typically triggers downstream reversals (e.g., inventory, accounting entries). This goes beyond a simple write/update and constitutes a destructive, non-undoable action with potentially wide financial and operational blast radius in an ERP context.
From the tool's definition Cancel a submitted document
Attacks that exploit this kind of access
Cancel a submitted 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 cancel_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.
cancel_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 cancel_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 cancel_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.
cancel_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 →