// SCAN REPORT

Phoenixd MCP Server

17 tools. 8 can modify or destroy data without limits.

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

Last updated: 30 Jun 2026

8 can modify or destroy data

9 read-only

17 tools total

Community server · catalogue entry verified 30/06/2026

How to control Phoenixd MCP Server ↓

TOOL MAP

What Phoenixd MCP Server exposes to your agents

Read (9) Write / Execute (3) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Phoenixd MCP Server tools

Financial · Critical pay-invoice This tool directly transfers cryptocurrency funds, which constitutes a financial transaction that moves money and creates irreversible obligations. Financial · Critical pay-lightning-address This tool initiates payment transactions on the Bitcoin Lightning Network. Financial · Critical pay-offer This tool directly moves money (sats/Bitcoin) by paying a BOLT12 offer on the Lightning Network. Financial · Critical pay-on-chain This tool directly commits financial obligations by transferring on-chain Bitcoin to a specified address.

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

POLICY

How to control Phoenixd MCP Server

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

Block financial tools by default

{
  "bump-fee": {
    "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

{
  "close-channel": {
    "limits": [
      {
        "counter": "close-channel_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "decode-invoice": {
    "limits": [
      {
        "counter": "decode-invoice_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 Phoenixd 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 PHOENIXD →

Instant setup, no code required.

FULL CATALOGUE

All 17 Phoenixd MCP Server tools

FINANCIAL 5 tools

Financial bump-fee Makes all your unconfirmed transactions use a higher fee rate, using CPFP. Returns the ID of the child transac Financial pay-invoice Pay a bolt11 invoice with a specified amount and description Financial pay-lightning-address Pays an email-like Lightning address, either based on BIP-353 or LNURL Financial pay-offer Pay a bolt12 offer Financial pay-on-chain Pay an on-chain address with a specified amount and fee rate

WRITE 3 tools

Write close-channel Close a channel by ID, sending the funds to a specified address on chain, with a specified fee rate Write create-invoice Create a bolt11 invoice with a specified amount and description Write create-offer Create a bolt12 offer with an optional description and amount

READ 9 tools

Read decode-invoice Decode an bolt11 invoice, the output amount is in milisatoshis Read decode-offer Decode an bolt12 offer the output amount is in milisatoshis Read get-balance Get the balance of the node Read get-incoming-payment Get the incoming payment by payment hash Read get-node-info Get the node info Read get-outgoing-payment Get the outgoing payment by payment id Read list-channels List the node channels Read list-incoming-payments List the incoming payments Read list-outgoing-payments List the outgoing payments

EXPLORE

Related servers

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

FAQ

Questions about Phoenixd MCP Server

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

Yes. The Phoenixd MCP Server server exposes 5 financial tools including bump-fee, pay-invoice, 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 Phoenixd MCP Server? +

The Phoenixd MCP Server server has 3 write tools including close-channel, create-invoice, create-offer. 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 Phoenixd MCP Server.

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

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

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

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

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

ENFORCE POLICY ON PHOENIXD →

Instant setup, no code required.

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