permanent_delete_order
Permanently delete an already archived order in Sanka. Requires confirm=true and cannot be undone.
This record as markdown: /tools/sankahq-sanka-mcp/permanent-delete-order.md
What permanent_delete_order does on Sanka MCP Server
AI agents call permanent_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 permanent_delete_order is rated Critical
This tool performs irreversible deletion of order data. Even though deletion requires confirmation (confirm=true), it still permanently removes archived orders without any recovery mechanism. This is a classic Destructive action that cannot be undone, making it more severe than Write operations but likely not Financial (since the order is already archived, not active).
From the tool's definition Tool name 'permanent_delete_order' and description explicitly states 'Permanently delete' and 'cannot be undone', indicating irreversible data removal.
Attacks that exploit this kind of access
The rule that runs permanent_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 permanent_delete_order, this is the rule to start with:
permanent_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 permanent_delete_order call is checked against it from then on.
Questions about permanent_delete_order
Permanently delete an already archived order in Sanka. Requires confirm=true and cannot be undone. 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 permanent_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.
permanent_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 permanent_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 permanent_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.
permanent_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