Delete an invoice from sevdesk
AI agents call delete_invoice 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 invoice is a destructive operation that cannot be undone and removes authoritative financial records from the accounting system. This has high blast radius if an AI agent maliciously or erroneously deletes invoices, potentially affecting financial reconciliation, tax compliance, and audit trails.
From the tool's definition Tool name 'delete_invoice' and description 'Delete an invoice from sevdesk' explicitly indicate permanent removal of a financial document. The verb 'delete' combined with 'invoice' (a critical accounting record) demonstrates irreversible data destruction.
Attacks that exploit this kind of access
Delete an invoice 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_invoice: 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_invoice 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_invoice 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_invoice. 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_invoice 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 →