mark_invoice_paid
Mark a draft or sent invoice as paid (stamps paid_at). Cannot be applied to a void invoice. invoice_id is required.
This record as markdown: /tools/com-meta-council-decision-intelligence/mark-invoice-paid.md
What mark_invoice_paid does on Meta Council
AI agents use mark_invoice_paid to commit financial operations through Meta Council, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoice_id | string | Yes |
Parameters from the server's own tool schema.
Why mark_invoice_paid is rated Critical
Marking invoices as paid directly affects financial records and payment status irreversibly.
From the tool's definition Mark a draft or sent invoice as paid, stamps paid_at
Attacks that exploit this kind of access
The rule that runs mark_invoice_paid 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 mark_invoice_paid, this is the rule to start with:
Any call to mark_invoice_paid is blocked until a human approves 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 mark_invoice_paid call is checked against it from then on.
Questions about mark_invoice_paid
Mark a draft or sent invoice as paid (stamps paid_at). Cannot be applied to a void invoice. invoice_id is required. It is categorised as a Financial tool in the Meta Council MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
mark_invoice_paid 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 mark_invoice_paid: 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.
mark_invoice_paid is a Financial 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 mark_invoice_paid 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 mark_invoice_paid. 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.
mark_invoice_paid 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