get_invoice_status

Check if a created invoice has been paid. Use the payment_hash from create_invoice.

SERVERLightning Wallet SOURCElightning-wallet-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/get-invoice-status.md

WHAT IT DOES

What get_invoice_status does on Lightning Wallet

AI agents call get_invoice_status 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.

RISK

Why get_invoice_status is rated Low

This tool retrieves payment status information about an existing invoice without modifying, creating, or deleting any data. It is purely informational—checking whether a payment has already occurred. While it relates to financial data, the tool itself does not move money or commit financial obligations; it merely reports on transaction state.

From the tool's definition Tool description states 'Check if a created invoice has been paid', which is a query operation with no side effects. The verb 'check' and action 'has been paid' (past tense status inquiry) indicate retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_invoice_status 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_invoice_status, this is the rule to start with:

get_invoice_status Allowed

get_invoice_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_invoice_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every get_invoice_status call is checked against it from then on.

FAQ

Questions about get_invoice_status

What does the get_invoice_status tool do? +

Check if a created invoice has been paid. Use the payment_hash from create_invoice. It is categorised as a Read tool in the Lightning Wallet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_invoice_status? +

Register the Lightning Wallet MCP server in PolicyLayer and add a rule for get_invoice_status: 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.

What risk level is get_invoice_status? +

get_invoice_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_invoice_status? +

Yes. Add a rate_limit block to the get_invoice_status 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.

How do I block get_invoice_status completely? +

Set action: deny in the PolicyLayer policy for get_invoice_status. 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.

What MCP server provides get_invoice_status? +

get_invoice_status 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.

KEEP EXPLORING

More on Lightning Wallet, and thousands of servers like it.

This server

All 45 Lightning Wallet tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →