# pay_invoice

Pay a Lightning invoice

Agent View of the PolicyLayer registry record for `pay_invoice`. HTML page: https://policylayer.com/tools/abdelstark-bitcoin-mcp/pay-invoice

## Facts

- Tool: `pay_invoice`
- Server: Bitcoin MCP Server (`abdelstark/bitcoin-mcp`) — https://policylayer.com/tools/abdelstark-bitcoin-mcp.md
- Homepage: https://github.com/AbdelStark/bitcoin-mcp
- Risk category: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pay_invoice",
    "arguments": {}
  }
}
```

## Why pay_invoice is rated Critical

This tool commits financial obligations by transferring Bitcoin or stablecoins via the Lightning Network. Misuse by an AI agent could result in unauthorized payments, fund loss, and irreversible transactions. Financial category applies; severity is critical due to direct money movement and inability to undo payments once broadcast.

From the tool's own definition: "Tool name 'pay_invoice' combined with description 'Pay a Lightning invoice' indicates direct movement of cryptocurrency funds. Lightning Network is a Bitcoin payment layer where invoices represent actual payment obligations."

## Use case

AI agents use pay_invoice to commit financial operations through Bitcoin MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bitcoin MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pay_invoice": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Bitcoin MCP Server (6)

- `decode_invoice` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-invoice.md
- `decode_tx` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-tx.md
- `get_latest_block` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-latest-block.md
- `get_transaction` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-transaction.md
- `validate_address` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/validate-address.md
- `generate_key` — Write — https://policylayer.com/tools/abdelstark-bitcoin-mcp/generate-key.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdelstark-bitcoin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdelstark-bitcoin-mcp