List Lightning channels for the store's Lightning node.
AI agents call list_lightning_channels to retrieve information from BTCPay Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about Lightning channels—a passive data retrieval operation with no side effects. It does not create, modify, delete, execute code, or move funds. The 'list' verb and the informational nature of channel data listing classify it as Read severity low.
From the tool's definition Tool name 'list_lightning_channels' and description 'List Lightning channels' indicate a read-only query operation that retrieves information about existing Lightning network channels without modifying, executing code, or triggering external state changes.
Attacks that exploit this kind of access
List Lightning channels for the store's Lightning node. It is categorised as a Read tool in the BTCPay Server MCP MCP Server, which means it retrieves data without modifying state.
Register the BTCPay Server MCP server in PolicyLayer and add a rule for list_lightning_channels: 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 BTCPay Server MCP. Nothing to install.
list_lightning_channels 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_lightning_channels 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_lightning_channels. 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_lightning_channels is provided by the BTCPay Server MCP server (ThomsenDrake/btcpay-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 →