delete_order
Archive an order in Sanka by order id, numeric id, or external reference. This is a soft delete; use permanent_delete_order only after explicit confirmation.
This record as markdown: /tools/sankahq-sanka-mcp/delete-order.md
What delete_order does on Sanka MCP Server
AI agents call delete_order to permanently remove resources in Sanka MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_order is rated Critical
Although described as a 'soft delete' (archiving), the tool removes order data from active use and the description explicitly references a permanent deletion capability. Combined with the sibling tool 'activate_order' and the context that this is part of a financial/operational system (orders, invoices, payroll), deleting orders represents irreversible business-critical data destruction with significant operational…
From the tool's definition Tool name is 'delete_order' and description states it can 'Archive an order' and references 'permanent_delete_order', indicating irreversible data removal operations.
Attacks that exploit this kind of access
The rule that runs delete_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_order, this is the rule to start with:
delete_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every delete_order call is checked against it from then on.
Questions about delete_order
Archive an order in Sanka by order id, numeric id, or external reference. This is a soft delete; use permanent_delete_order only after explicit confirmation. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for delete_order: 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 Sanka MCP Server. Nothing to install.
delete_order 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_order 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_order. 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_order is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
Across the catalogue