List all connected messaging channels on the OpenClaw daemon
AI agents call list_channels to retrieve information from ClawDaemon MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing messaging channels without modifying, deleting, executing, or triggering any automation. It is a passive read operation that retrieves metadata about the daemon's configuration. The low severity reflects minimal blast radius: an AI agent with this tool can only discover what channels exist, not interact with or abuse them.
From the tool's definition Tool name is 'list_channels' and description states it 'List[s] all connected messaging channels' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all connected messaging channels on the OpenClaw daemon. It is categorised as a Read tool in the ClawDaemon MCP MCP Server, which means it retrieves data without modifying state.
Register the ClawDaemon 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 ClawDaemon MCP. 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 ClawDaemon MCP server (mordiaky/clawdaemon-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 →