decode_invoice
Decode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/decode-invoice.md
What decode_invoice does on Lightning Wallet
AI agents call decode_invoice to retrieve information from Lightning Wallet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why decode_invoice is rated Low
This tool only parses and reads the contents of a BOLT11 invoice string. It explicitly states it does not pay the invoice, making it a pure read/query operation with no side effects or financial obligations.
From the tool's definition Decode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination.
Attacks that exploit this kind of access
The rule that runs decode_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 decode_invoice, this is the rule to start with:
decode_invoice is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every decode_invoice call is checked against it from then on.
Questions about decode_invoice
Decode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination. It is categorised as a Read tool in the Lightning Wallet MCP Server, which means it retrieves data without modifying state.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for decode_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.
decode_invoice is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the decode_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 decode_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.
decode_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.
This server
Across the catalogue