pay_lightning_address

THE RISK

Critical Risk

Why pay_lightning_address needs a policy

This tool sends cryptocurrency (Lightning Network satoshis) to a recipient address, which constitutes an irreversible financial obligation and transfer of value. Even a small misconfiguration or incorrect address could result in permanent loss of funds. This is the most severe category and warrants critical severity due to the irreversible nature of blockchain transactions and potential for financial loss.

From the tool's definition Tool is named 'pay_lightning_address' and explicitly described as 'Send sats to a Lightning address'. Sats are Bitcoin satoshis (smallest unit of Bitcoin). This directly moves cryptocurrency funds, which is a financial transaction.

Documented attack patterns abuse exactly the kind of access pay_lightning_address gives an agent:

POLICY

How to control pay_lightning_address

PolicyLayer is an MCP gateway — it sits between your AI agents and LNbits MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pay_lightning_address:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pay_lightning_address": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to pay_lightning_address is blocked until a human approves it. The rest of the server keeps working.

Create a free account and register LNbits MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More LNbits MCP Server tools

Execute refresh_tools Re-fetch the OpenAPI spec from LNbits and rebuild the tool list. Write configure_lnbits Configure LNbits connection parameters at runtime. Read get_configuration Show current LNbits configuration with masked API keys. Read list_extensions Show all discovered extensions and their tool counts. Read test_connection Test the current LNbits connection by making a test API call.

All 6 LNbits MCP Server tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in LNbits MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about pay_lightning_address

What does the pay_lightning_address tool do? +

Send sats to a Lightning address (user@domain.com). It is categorised as a Financial tool in the LNbits MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on pay_lightning_address? +

Register the LNbits MCP Server MCP server in PolicyLayer and add a rule for pay_lightning_address: 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 LNbits MCP Server. Nothing to install.

What risk level is pay_lightning_address? +

pay_lightning_address is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pay_lightning_address? +

Yes. Add a rate_limit block to the pay_lightning_address 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 pay_lightning_address completely? +

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

pay_lightning_address is provided by the LNbits MCP Server MCP server (lnbits/lnbits-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LNbits MCP Server tool call.

Start from LNbits MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →