List the node channels
AI agents call list-channels to retrieve information from Phoenixd 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 displays channel information with no side effects. It is a simple data query operation. While the server overall handles financial operations (Bitcoin/Lightning), this specific tool only reads channel state and poses minimal risk if misused by an LLM agent—it cannot move funds, delete channels, or trigger external operations.
From the tool's definition Tool name 'list-channels' and description 'List the node channels' indicate a read-only query operation that retrieves information about existing Lightning Network channels without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
List the node channels. It is categorised as a Read tool in the Phoenixd MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Phoenixd MCP Server MCP server in PolicyLayer and add a rule for list-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 Phoenixd MCP Server. Nothing to install.
list-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-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-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-channels is provided by the Phoenixd MCP Server MCP server (sharmaz/phoenixd-mcp-server). 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 →