withdraw
Withdraw funds from operator account to external Lightning invoice. REQUIRES OPERATOR KEY. Subject to security cooldown.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/withdraw.md
What withdraw does on Lightning Wallet
AI agents use withdraw to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why withdraw is rated Critical
This tool directly transfers money (Bitcoin via Lightning Network) out of the operator's account to external parties. This is irreversible fund movement, triggering a financial obligation/loss from the operator's perspective. Even with the operator key requirement and cooldown as mitigations, misuse by a compromised agent could drain the operator's funds. Financial category is the most severe applicable.
From the tool's definition Tool description explicitly states 'Withdraw funds from operator account to external Lightning invoice' — this moves cryptocurrency from the operator's wallet to an external recipient.
Attacks that exploit this kind of access
The rule that runs withdraw 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 withdraw, this is the rule to start with:
Any call to withdraw 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 withdraw call is checked against it from then on.
Questions about withdraw
Withdraw funds from operator account to external Lightning invoice. REQUIRES OPERATOR KEY. Subject to security cooldown. 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 withdraw: 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.
withdraw 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 withdraw 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 withdraw. 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.
withdraw 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