create_invoice
AI agents use create_invoice to commit financial operations through BTCPay Server MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating an invoice in BTCPay Server initiates a payment obligation — it generates a request for funds from a payer. This is a financial operation that commits a monetary transaction flow. Even though the description is empty, the tool name combined with the server's explicit financial/payment purpose strongly indicates a Financial category.
From the tool's definition Tool name 'create_invoice' on a BTCPay Server MCP described as managing 'invoices, payments, stores, webhooks, Lightning'; sibling tools include 'create_payment_request' and 'create_pull_payment', confirming financial context.
Attacks that exploit this kind of access
create_invoice. It is categorised as a Financial tool in the BTCPay Server MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the BTCPay Server 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 BTCPay Server MCP. 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 BTCPay Server MCP server (ThomsenDrake/btcpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →