// SCAN REPORT

LNbits MCP Server

6 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

3 can modify or destroy data

3 read-only

6 tools total

Community server · catalogue entry verified 12/06/2026

How to control LNbits MCP Server ↓

TOOL MAP

What LNbits MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous LNbits MCP Server tools

Financial · Critical pay_lightning_address This tool sends cryptocurrency (Lightning Network satoshis) to a recipient address, which constitutes an irreversible financial obligation and transfer of value. Execute · Medium refresh_tools This tool triggers an external operation (fetching from LNbits) and rebuilds/modifies the active tool list, which is a dynamic execution action with side effects on the agent's available capabilities. Write · High configure_lnbits This tool creates or modifies configuration data at runtime.

3 of LNbits MCP Server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control LNbits MCP Server

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

Block financial tools by default

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

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

Rate limit write operations

{
  "configure_lnbits": {
    "limits": [
      {
        "counter": "configure_lnbits_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_configuration": {
    "limits": [
      {
        "counter": "get_configuration_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 LNbits MCP Server — 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 LNBITS →

Free to start. No card required.

FULL CATALOGUE

All 6 LNbits MCP Server tools

FINANCIAL 1 tools

Financial pay_lightning_address Send sats to a Lightning address (user@domain.com).

EXECUTE 1 tools

Execute refresh_tools Re-fetch the OpenAPI spec from LNbits and rebuild the tool list.

WRITE 1 tools

Write configure_lnbits Configure LNbits connection parameters at runtime.

READ 3 tools

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.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about LNbits MCP Server

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

Yes. The LNbits MCP Server server exposes 1 financial tools including pay_lightning_address. 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 do I prevent bulk modifications through LNbits MCP Server? +

The LNbits MCP Server server has 1 write tools including configure_lnbits. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach LNbits MCP Server.

How many tools does the LNbits MCP Server MCP server expose? +

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

How do I enforce a policy on LNbits MCP Server? +

Register the LNbits MCP Server 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 LNbits MCP Server tool call.

Deterministic rules across all 6 LNbits MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LNBITS →

Free to start. No card required.

6 LNbits MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.