delete_invoice
Delete a DRAFT invoice. Only invoices that have never been sent can be deleted; otherwise use void_invoice.
This record as markdown: /tools/io-favcrm-favcrm/delete-invoice.md
What delete_invoice does on FavCRM
AI agents call delete_invoice to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoiceId | string | Yes | Invoice ID to delete |
Parameters from the server's own tool schema.
Why delete_invoice is rated Critical
Deleting invoices is a destructive action that irreversibly removes financial transaction records. While limited to DRAFT invoices that have never been sent, deletion still represents permanent data loss that cannot be recovered through normal operations. In a business context, this impacts accounting records and financial auditing.
From the tool's definition Tool name is 'delete_invoice' and description states 'Delete a DRAFT invoice.' The verb 'delete' combined with the irreversible removal of financial records indicates destructive capability.
Attacks that exploit this kind of access
The rule that runs delete_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_invoice, this is the rule to start with:
delete_invoice 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 FavCRM, apply this rule, and every delete_invoice call is checked against it from then on.
Questions about delete_invoice
Delete a DRAFT invoice. Only invoices that have never been sent can be deleted; otherwise use void_invoice. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_invoice accepts 1 parameter: invoiceId. Required: invoiceId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
Across the catalogue