pay_l402_api

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-l402-api.md

WHAT IT DOES

What pay_l402_api does on Lightning Wallet

AI agents use pay_l402_api 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_l402_api is rated Critical

This tool commits financial obligations by automatically initiating payments (Lightning and USDC transfers) in response to API responses. Even though payment is conditional (HTTP 402), the tool autonomously decides to spend the agent's funds. This is the most severe category (Financial > Destructive > Execute > Write > Read).

From the tool's definition Tool description states it 'automatically' pays via 'Lightning' and 'USDC on Base' protocols when HTTP 402 is returned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pay_l402_api Approval-gated

Any call to pay_l402_api 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_l402_api": {
      "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_l402_api call is checked against it from then on.

FAQ

Questions about pay_l402_api

What does the pay_l402_api tool do? +

Make a request to a paid API. Supports L402 (Lightning) and X402 (USDC on Base) protocols. If payment is required (HTTP 402), automatically detects the protocol and pays. L402 is preferred when both are available. REQUIRES 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_l402_api? +

Register the Lightning Wallet MCP server in PolicyLayer and add a rule for pay_l402_api: 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_l402_api? +

pay_l402_api 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_l402_api? +

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

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

pay_l402_api 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 → Critical-risk tools on this server →

Across the catalogue

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 →