l402-pay

SERVER402 SOURCE402-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/dev-forgesworn-402-mcp/l402-pay.md

WHAT IT DOES

What l402-pay does on 402

AI agents use l402-pay to commit financial operations through 402, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why l402-pay is rated Critical

This tool directly moves money by confirming payment on the Lightning Network. It irreversibly commits financial obligations through settlement polling. Even though the user initiates the payment via wallet, this tool executes the confirmation and settlement, which constitutes a Financial operation with critical severity due to the autonomous nature of the MCP server (agents can call this without human intervention…

From the tool's definition Tool description explicitly states 'Confirm payment and store credentials' and 'polls the payment server for settlement', indicating it commits financial transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs l402-pay safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For l402-pay, this is the rule to start with:

l402-pay Approval-gated

Any call to l402-pay 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": {
    "l402-pay": {
      "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 402, apply this rule, and every l402-pay call is checked against it from then on.

FAQ

Questions about l402-pay

What does the l402-pay tool do? +

Confirm payment and store credentials. Call this after l402-fetch returns a 402 with a paymentHash — polls the payment server for settlement (up to 30s for human wallet), then stores the credential so the next l402-fetch succeeds. For human wallets, call this immediately after showing the payment URL to the user. It is categorised as a Financial tool in the 402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on l402-pay? +

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

What risk level is l402-pay? +

l402-pay 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 l402-pay? +

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

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

l402-pay is provided by the 402 MCP server (402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 402, and thousands of servers like it.

This server

All 10 402 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 →