Get Lightning wallet balance and channel liquidity
AI agents call ldk_get_balance 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 only retrieves financial information (balance and liquidity data) without modifying, executing operations, or committing any transactions. It is purely informational and has no destructive or side-effecting capabilities. The blast radius if misused is minimal—an attacker could only learn the wallet's financial state, not alter it.
From the tool's definition Tool name 'ldk_get_balance' and description 'Get Lightning wallet balance and channel liquidity' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of balance queries confirm this is a data retrieval function.
Attacks that exploit this kind of access
Get Lightning wallet balance and channel liquidity. 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_get_balance: 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_get_balance 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_get_balance 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_get_balance. 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_get_balance 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 →