create_invoice
Create a new invoice for a customer
This record as markdown: /tools/stripe/create-invoice.md
What create_invoice does on Stripe
AI agents use create_invoice to commit financial operations through Stripe, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why create_invoice is rated Critical
Creating invoices commits financial obligations by generating billable charges for customers. While not a direct payment execution, invoices are legally binding financial instruments that obligate payment. The sibling tools (create_refund, create_payment_link, cancel_subscription) confirm this is a financial transaction server.
From the tool's definition Tool named 'create_invoice' with description 'Create a new invoice for a customer' on Stripe server. Invoices are financial documents that create payment obligations and trigger billing workflows.
Risk signalsCreates invoices sent to customers
Attacks that exploit this kind of access
The rule that runs create_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 create_invoice, this is the rule to start with:
Any call to create_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 create_invoice call is checked against it from then on.
Questions about create_invoice
Create a new invoice for a customer. 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 create_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.
create_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 create_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 create_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.
create_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