Test payment flows by paying a Lightning invoice
AI agents use ldk_pay_invoice to commit financial operations through LDK MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes actual payments on the Lightning Network, transferring real monetary value. Even though framed as 'testing,' it commits financial obligations by sending funds to invoice recipients. This is the most severe risk category (Financial > Destructive > Execute > Write > Read). Misuse by an AI agent could result in unauthorized fund transfers. Critical severity due to direct monetary loss potential.
From the tool's definition Tool name 'ldk_pay_invoice' and description 'Test payment flows by paying a Lightning invoice' indicate it sends payments over the Lightning Network.
Attacks that exploit this kind of access
Test payment flows by paying a Lightning invoice. It is categorised as a Financial tool in the LDK MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the LDK MCP Server MCP server in PolicyLayer and add a rule for ldk_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 LDK MCP Server. Nothing to install.
ldk_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 ldk_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 ldk_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.
ldk_pay_invoice is provided by the LDK MCP Server MCP server (stevengeller/ldk-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 →