Decode an RGB Lightning invoice
AI agents call rgb_decode_lightning_invoice to retrieve information from RGB Lightning Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Decoding an invoice is a read-only operation that parses and extracts information from an existing invoice structure. It has no side effects, does not execute transactions, create payment obligations, or modify any data. The operation is purely informational, similar to parsing or querying data.
From the tool's definition Tool name 'rgb_decode_lightning_invoice' and description 'Decode an RGB Lightning invoice' indicate retrieval and parsing of invoice data without modification or execution of payment operations.
Attacks that exploit this kind of access
Decode an RGB Lightning invoice. It is categorised as a Read tool in the RGB Lightning Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RGB Lightning Network MCP Server MCP server in PolicyLayer and add a rule for rgb_decode_lightning_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 RGB Lightning Network MCP Server. Nothing to install.
rgb_decode_lightning_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 rgb_decode_lightning_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 rgb_decode_lightning_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.
rgb_decode_lightning_invoice is provided by the RGB Lightning Network MCP Server MCP server (lnfi-network/rgb-mcp-server). 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 →