channel → pinned session_id. Doesn't tell you whether work is
AI agents call list_channels to retrieve information from Claude Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists channel-to-session mappings without modifying, executing, or destroying anything. It is a passive data retrieval operation typical of Read-category tools. The low severity reflects that listing metadata about channels has minimal blast radius even if misused by an agent.
From the tool's definition Tool name 'list_channels' and description 'channel → pinned session_id' indicate a query/retrieval operation. The phrase 'Doesn't tell you whether work is' (incomplete but contextually a qualifier) suggests this is informational only with no side effects.
Attacks that exploit this kind of access
channel → pinned session_id. Doesn't tell you whether work is. It is categorised as a Read tool in the Claude Bridge MCP Server, which means it retrieves data without modifying state.
Register the Claude Bridge 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 Claude Bridge. 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 Claude Bridge MCP server (josiahsiegel/claude-bridge). 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 →