pay_lightning_address

Pay to a Lightning address (user@domain.com format). Works with an operator key (pays from the operator wallet) or an agent key.

SERVERLightning Wallet SOURCElightning-wallet-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/pay-lightning-address.md

WHAT IT DOES

What pay_lightning_address does on Lightning Wallet

AI agents use pay_lightning_address to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why pay_lightning_address is rated Critical

Tool directly transfers Bitcoin funds via Lightning Network, committing financial obligations irreversibly.

From the tool's definition Pay to a Lightning address. Moves money from wallet via operator or agent key.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pay_lightning_address Approval-gated

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

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pay_lightning_address

What does the pay_lightning_address tool do? +

Pay to a Lightning address (user@domain.com format). Works with an operator key (pays from the operator wallet) or an agent key. 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.

How do I enforce a policy on pay_lightning_address? +

Register the Lightning Wallet 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 Lightning Wallet. 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 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 59 Lightning Wallet tools → Critical-risk tools on this server →

Across the catalogue

pay_domain on 262 →pay_x402 on 8004swap →pay_invoice on Bitcoin MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →