void_invoice
Void an invoice. Destructive — invoice can no longer be paid or edited; existing payments are preserved as history. Cannot void invoices that are already PAID or VOIDED.
This record as markdown: /tools/io-favcrm-favcrm/void-invoice.md
What void_invoice does on FavCRM
AI agents call void_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 void |
Parameters from the server's own tool schema.
Why void_invoice is rated Critical
Voiding an invoice is explicitly labeled destructive and irreversible — the invoice permanently loses its ability to be paid or edited. This is a one-way, non-undoable state change that eliminates the financial utility of the invoice, qualifying as Destructive (more severe than Write). While it touches financial records, it does not move money or commit financial obligations, so Destructive takes precedence.
From the tool's definition Void an invoice. Destructive — invoice can no longer be paid or edited; existing payments are preserved as history.
Attacks that exploit this kind of access
The rule that runs void_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 void_invoice, this is the rule to start with:
void_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 void_invoice call is checked against it from then on.
Questions about void_invoice
Void an invoice. Destructive — invoice can no longer be paid or edited; existing payments are preserved as history. Cannot void invoices that are already PAID or VOIDED. 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.
void_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 void_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.
void_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 void_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 void_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.
void_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