AI agents use pay_invoice to commit financial operations through Bitcoin MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool commits financial obligations by transferring Bitcoin or stablecoins via the Lightning Network. Misuse by an AI agent could result in unauthorized payments, fund loss, and irreversible transactions. Financial category applies; severity is critical due to direct money movement and inability to undo payments once broadcast.
From the tool's definition Tool name 'pay_invoice' combined with description 'Pay a Lightning invoice' indicates direct movement of cryptocurrency funds. Lightning Network is a Bitcoin payment layer where invoices represent actual payment obligations.
Documented attack patterns abuse exactly the kind of access pay_invoice gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pay_invoice:
{
"version": "1",
"default": "deny",
"tools": {
"pay_invoice": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to pay_invoice is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Pay a Lightning invoice. It is categorised as a Financial tool in the Bitcoin MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitcoin MCP Server MCP server in PolicyLayer and add a rule for pay_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 Bitcoin MCP Server. Nothing to install.
pay_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 pay_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 pay_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.
pay_invoice is provided by the Bitcoin MCP Server MCP server (abdelstark/bitcoin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Bitcoin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Bitcoin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.