Close a Lightning channel cooperatively or force close
AI agents call ldk_close_channel to permanently remove resources in LDK MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a Lightning channel, whether cooperatively or via force-close, permanently destroys the channel state and commits funds to an on-chain settlement. This cannot be reversed once initiated (especially force-close). The action has high blast radius as it terminates payment channel relationships and may lock funds in time-locked outputs.
From the tool's definition 'Close a Lightning channel cooperatively or force close' — closing a Lightning channel is an irreversible action that settles the channel on-chain and cannot be undone
Attacks that exploit this kind of access
Close a Lightning channel cooperatively or force close. It is categorised as a Destructive tool in the LDK MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LDK MCP Server MCP server in PolicyLayer and add a rule for ldk_close_channel: 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_close_channel is a Destructive 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 ldk_close_channel 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_close_channel. 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_close_channel 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 →