List recent Lightning payments with status
AI agents call ldk_list_payments to retrieve information from LDK 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 and queries payment history data without modifying state, executing external operations, or causing side effects. It is a straightforward read operation analogous to fetching payment records from a ledger. The severity is low because exposure of payment history data, while potentially sensitive, does not enable direct financial transactions, code execution, or data destruction.
From the tool's definition Tool name includes 'list' and description states 'List recent Lightning payments with status' — a pure query operation with no modification or execution.
Attacks that exploit this kind of access
List recent Lightning payments with status. It is categorised as a Read tool in the LDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LDK MCP Server MCP server in PolicyLayer and add a rule for ldk_list_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 LDK MCP Server. Nothing to install.
ldk_list_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 ldk_list_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 ldk_list_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.
ldk_list_payments is provided by the LDK MCP Server MCP server (stevengeller/ldk-mcp). 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 →