Delete an order from sevdesk
AI agents call delete_order to permanently remove resources in Sevdesk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an order is a destructive action that permanently removes business-critical data from the sevdesk accounting system. Orders represent financial transactions and business commitments; their deletion cannot be reversed. The blast radius is high because an AI agent misusing this tool could delete important order records, disrupting financial records, customer relationships, and business continuity.
From the tool's definition Tool name 'delete_order' and description 'Delete an order from sevdesk' explicitly indicate irreversible deletion of business data (orders). This is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete an order from sevdesk. It is categorised as a Destructive tool in the Sevdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sevdesk 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 Sevdesk. 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 Sevdesk MCP server (codestra/sevdesk-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 →