void_invoice
Void a draft or sent invoice. Cannot be applied to an already-paid invoice (issue a credit note instead). invoice_id is required. No delete tool is exposed over MCP — void is the terminal non-destructive state.
This record as markdown: /tools/com-meta-council-decision-intelligence/void-invoice.md
What void_invoice does on Meta Council
AI agents call void_invoice to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoice_id | string | Yes |
Parameters from the server's own tool schema.
Why void_invoice is rated Critical
Although the tool description claims voiding is 'non-destructive,' the practical effect is irreversible termination of a financial document. This is a core characteristic of the Destructive category. Voiding cannot be undone without manual intervention (e.g., issuing corrective documents), making it more severe than Write (reversible modification).
From the tool's definition 'Void a draft or sent invoice' — voiding an invoice is an irreversible financial operation that terminates the invoice's validity and cannot be undone. The description explicitly notes this is 'the terminal non-destructive state,' emphasizing finality.
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 Meta Council, 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 Meta Council, apply this rule, and every void_invoice call is checked against it from then on.
Questions about void_invoice
Void a draft or sent invoice. Cannot be applied to an already-paid invoice (issue a credit note instead). invoice_id is required. No delete tool is exposed over MCP — void is the terminal non-destructive state. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
void_invoice accepts 1 parameter: invoice_id. Required: invoice_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council 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 Meta Council. 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 Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue