Delete an invoice
AI agents call siigo_delete_invoice to permanently remove resources in Siigo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an invoice in accounting software is a destructive action that cannot be undone and irreversibly removes a financial record. This could affect audits, tax compliance, and financial reporting. While not directly moving money (Financial category), it is more severe than Write operations because the deletion cannot be reversed.
From the tool's definition Tool name is 'siigo_delete_invoice' with description 'Delete an invoice'. The verb 'delete' combined with operating on financial documents (invoices) in accounting software indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an invoice. It is categorised as a Destructive tool in the Siigo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Siigo MCP Server MCP server in PolicyLayer and add a rule for siigo_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 Siigo MCP Server. Nothing to install.
siigo_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 siigo_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 siigo_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.
siigo_delete_invoice is provided by the Siigo MCP Server MCP server (jdlar1/siigo-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 →