Delete a voucher position
AI agents call delete_voucher_position 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.
This tool performs an irreversible delete operation on voucher position data. While not a direct financial transaction (no money movement), deletion of voucher positions in an accounting system destroys data and could obscure financial records, making it Destructive rather than Write.
From the tool's definition Tool name is 'delete_voucher_position' with description 'Delete a voucher position'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a voucher position. 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_voucher_position: 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_voucher_position 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_voucher_position 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_voucher_position. 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_voucher_position 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 →