Estimate Lightning routing fees for a payment
AI agents call ldk_estimate_fee 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 performs a read-only estimation of Lightning Network routing fees. It retrieves data about potential fees for a hypothetical payment without creating channels, moving funds, or executing any irreversible operations. The verb 'estimate' confirms it is a calculation/query rather than an action that commits financial changes.
From the tool's definition Tool name 'ldk_estimate_fee' and description 'Estimate Lightning routing fees for a payment' indicate a query operation that retrieves fee information without modifying state or executing transactions.
Attacks that exploit this kind of access
Estimate Lightning routing fees for a payment. 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_estimate_fee: 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_estimate_fee 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_estimate_fee 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_estimate_fee. 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_estimate_fee 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 →