finalize_invoice
Finalise and send an invoice for payment
This record as markdown: /tools/stripe/finalize-invoice.md
What finalize_invoice does on Stripe
AI agents use finalize_invoice to commit financial operations through Stripe, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why finalize_invoice is rated Critical
This tool commits an invoice for payment collection, which moves a customer toward financial obligation or payment processing. Combined with sibling tools (create_refund, create_invoice, create_payment_link, create_subscription), this is clearly part of Stripe's payment processing system.
From the tool's definition Tool name 'finalize_invoice' and description 'Finalise and send an invoice for payment' indicates commitment of a financial obligation. Stripe context confirms this is a payment/billing system.
Risk signalsTriggers real payment collection from customers
Attacks that exploit this kind of access
The rule that runs finalize_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stripe, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For finalize_invoice, this is the rule to start with:
Any call to finalize_invoice is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stripe, apply this rule, and every finalize_invoice call is checked against it from then on.
Questions about finalize_invoice
Finalise and send an invoice for payment. It is categorised as a Financial tool in the Stripe MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stripe MCP server in PolicyLayer and add a rule for finalize_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 Stripe. Nothing to install.
finalize_invoice 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 finalize_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 finalize_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.
finalize_invoice is provided by the Stripe MCP server (@modelcontextprotocol/server-stripe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stripe, and thousands of servers like it.
Across the catalogue