List the incoming payments
AI agents call list-incoming-payments to retrieve information from Phoenixd MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about incoming payments to a Bitcoin Lightning wallet. It is a read-only query operation with no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an unauthorized read of payment history could expose transaction details but cannot directly harm the wallet or financial position.
From the tool's definition Tool name 'list-incoming-payments' and description 'List the incoming payments' indicate a query operation that retrieves payment history without modifying data.
Attacks that exploit this kind of access
List the incoming payments. It is categorised as a Read tool in the Phoenixd MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Phoenixd MCP Server MCP server in PolicyLayer and add a rule for list-incoming-payments: 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.
list-incoming-payments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-incoming-payments 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 list-incoming-payments. 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.
list-incoming-payments 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 →