Pay a Lightning Network invoice
AI agents use rgb_pay_lightning_invoice to commit financial operations through RGB Lightning Network MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Paying an invoice commits financial obligation and moves value (cryptocurrency). This is irreversible once confirmed on the blockchain. An AI agent misusing this tool could transfer funds to incorrect addresses, overpay, or execute unauthorized payments, resulting in loss of user assets.
From the tool's definition Tool description states 'Pay a Lightning Network invoice' — a direct money transfer operation on the Lightning Network, a payment protocol built on Bitcoin.
Attacks that exploit this kind of access
Pay a Lightning Network invoice. It is categorised as a Financial tool in the RGB Lightning Network MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the RGB Lightning Network MCP Server MCP server in PolicyLayer and add a rule for rgb_pay_lightning_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 RGB Lightning Network MCP Server. Nothing to install.
rgb_pay_lightning_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 rgb_pay_lightning_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 rgb_pay_lightning_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.
rgb_pay_lightning_invoice is provided by the RGB Lightning Network MCP Server MCP server (lnfi-network/rgb-mcp-server). 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 →