keysend
Send a payment directly to a node without an invoice (keysend/spontaneous payment). REQUIRES AGENT KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/keysend.md
What keysend does on Lightning Wallet
AI agents use keysend to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why keysend is rated Critical
This tool moves Bitcoin funds over the Lightning Network directly to another node without requiring an invoice, constituting a financial transaction that cannot be reversed once broadcast. Misuse could result in loss of funds with no recovery path.
From the tool's definition "Send a payment directly to a node without an invoice (keysend/spontaneous payment)"
Attacks that exploit this kind of access
The rule that runs keysend safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For keysend, this is the rule to start with:
Any call to keysend is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every keysend call is checked against it from then on.
Questions about keysend
Send a payment directly to a node without an invoice (keysend/spontaneous payment). REQUIRES AGENT KEY. It is categorised as a Financial tool in the Lightning Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for keysend: 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 Lightning Wallet. Nothing to install.
keysend 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 keysend 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 keysend. 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.
keysend is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lightning Wallet, and thousands of servers like it.
Across the catalogue