// SCAN REPORT

BTCPay Server MCP

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

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

Last updated: 2 Jul 2026

5 can modify or destroy data

16 read-only

21 tools total

Community server · catalogue entry verified 02/07/2026

How to control BTCPay Server MCP ↓

TOOL MAP

What BTCPay Server MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous BTCPay Server MCP tools

Financial · High create_payment_request BTCPay Server is explicitly a payment processor. Financial · High refund_invoice Refunds move money back to customers and represent irreversible financial commitments. Financial · High create_invoice Creating an invoice in BTCPay Server initiates a payment obligation — it generates a request for funds from a payer. Write · High create_pull_payment A pull payment is a reversible financial authorization mechanism (creating a pull payment request does not immediately move funds).

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

POLICY

How to control BTCPay Server MCP

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

Block financial tools by default

{
  "create_invoice": {
    "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

{
  "create_pull_payment": {
    "limits": [
      {
        "counter": "create_pull_payment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_exchange_rate": {
    "limits": [
      {
        "counter": "get_exchange_rate_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 BTCPay Server MCP — 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 BTCPAY SERVER →

Instant setup, no code required.

FULL CATALOGUE

All 21 BTCPay Server MCP tools

FINANCIAL 3 tools

Financial create_invoice create_invoice Financial create_payment_request create_payment_request Financial refund_invoice refund_invoice

WRITE 2 tools

Write create_pull_payment create_pull_payment Write create_webhook create_webhook

READ 16 tools

Read get_exchange_rate Get the current BTCPay exchange rate for a currency pair. Read get_invoice Get details and status of a BTCPay invoice. Read get_lightning_info Get Lightning node info and balance for the store. Read get_payment_request Get details of a specific payment request. Read get_server_info Get BTCPay Server version and system information. Read get_store_info Get detailed information about a specific BTCPay store. Read get_store_payment_methods List payment methods enabled for a BTCPay store. Read get_wallet_balance get_wallet_balance Read list_invoices List invoices from the default BTCPay store. Read list_lightning_channels List Lightning channels for the store's Lightning node. Read list_payment_requests List all payment requests (reusable payment links) for the store. Read list_payouts List all payouts (actual payout transactions) for the store. Read list_pull_payments list_pull_payments Read list_stores List all BTCPay Server stores accessible with the current API key. Read list_wallet_transactions List on-chain wallet transactions for a payment method. Read list_webhooks List all webhooks configured for the store.

EXPLORE

Related servers

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

FAQ

Questions about BTCPay Server MCP

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

Yes. The BTCPay Server MCP server exposes 3 financial tools including create_invoice, create_payment_request, refund_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 do I prevent bulk modifications through BTCPay Server MCP? +

The BTCPay Server MCP server has 2 write tools including create_pull_payment, create_webhook. 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 BTCPay Server MCP.

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

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

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

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

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

ENFORCE POLICY ON BTCPAY SERVER →

Instant setup, no code required.

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