get_deposit_invoice
Create a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/get-deposit-invoice.md
What get_deposit_invoice does on Lightning Wallet
AI agents use get_deposit_invoice to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why get_deposit_invoice is rated Critical
This tool initiates a Bitcoin Lightning Network payment flow by creating an invoice intended to move real funds (sats) into an account. While creating an invoice alone doesn't move money, it is a direct step in committing a financial transaction (depositing sats), making it Financial in nature. Misuse could lead to unintended fund movements or phishing-style invoice generation.
From the tool's definition 'Create a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance.'
Attacks that exploit this kind of access
The rule that runs get_deposit_invoice 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 get_deposit_invoice, this is the rule to start with:
Any call to get_deposit_invoice 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 get_deposit_invoice call is checked against it from then on.
Questions about get_deposit_invoice
Create a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance. 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 get_deposit_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 Lightning Wallet. Nothing to install.
get_deposit_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 get_deposit_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 get_deposit_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.
get_deposit_invoice 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