Pay a bolt11 invoice with a specified amount and description
AI agents use pay-invoice to commit financial operations through Phoenixd MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly transfers cryptocurrency funds, which constitutes a financial transaction that moves money and creates irreversible obligations. Combined with the server context showing this is a Bitcoin Lightning wallet management tool, the severity is critical due to the potential for significant monetary loss if misused by an AI agent. Financial category takes precedence over Execute category.
From the tool's definition Tool enables payment of Bitcoin Lightning invoices, described as 'Pay a bolt11 invoice with a specified amount and description'. This directly commits financial obligations and moves money on the Bitcoin Lightning Network.
Attacks that exploit this kind of access
Pay a bolt11 invoice with a specified amount and description. It is categorised as a Financial tool in the Phoenixd MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Phoenixd MCP Server MCP server in PolicyLayer and add a rule for pay-invoice: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Phoenixd MCP Server. Nothing to install.
pay-invoice is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pay-invoice rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for pay-invoice. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
pay-invoice is provided by the Phoenixd MCP Server MCP server (sharmaz/phoenixd-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →