// SCAN REPORT

Lightningprox

5 tools. 2 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control Lightningprox ↓

TOOL MAP

What Lightningprox exposes to your agents

Read (3) Write / Execute (0) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Lightningprox tools

Financial · High chat Each call to this tool spends Bitcoin Lightning tokens (sats) to pay for AI model access. Financial · High generate_invoice This tool initiates a financial transaction by generating a Bitcoin Lightning payment invoice.

2 of Lightningprox's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Lightningprox

PolicyLayer is an MCP gateway — it sits between your AI agents and Lightningprox, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "chat": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "check_payment": {
    "limits": [
      {
        "counter": "check_payment_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Lightningprox — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LIGHTNINGPROX →

Instant setup, no code required.

FULL CATALOGUE

All 5 Lightningprox tools

FINANCIAL 2 tools

Financial chat Send a message to an AI model via LightningProx. Pay per request with a Lightning spend token. Supports 19 mod Financial generate_invoice Generate a Bitcoin Lightning invoice to top up a LightningProx spend token. Returns a BOLT11 payment request a

READ 3 tools

Read check_payment Check if a Lightning invoice has been paid and retrieve the spend token. Poll this after generate_invoice unti Read get_balance Check the remaining balance on a LightningProx spend token. Returns balance in sats. Uses LIGHTNINGPROX_SPEND_ Read list_models List all AI models available through LightningProx. Returns model IDs, names, providers, and pricing. 19 model

FAQ

Questions about Lightningprox

Can an AI agent move money through the Lightningprox MCP server? +

Yes. The Lightningprox server exposes 2 financial tools including chat, generate_invoice. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the Lightningprox MCP server expose? +

5 tools across 2 categories: Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Lightningprox? +

Register the Lightningprox MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lightningprox tool call.

Deterministic rules across all 5 Lightningprox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LIGHTNINGPROX →

Instant setup, no code required.

5 Lightningprox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.