AI agents call cmux_list_panels to retrieve information from Cmux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
cmux_list_panels retrieves and enumerates existing panels/terminal surfaces for informational purposes only. There is no data modification, code execution, deletion, or financial impact. This is a straightforward inventory or discovery operation, making it a Read-category tool with low severity since listing panels poses minimal risk even if misused by an agent.
From the tool's definition Tool description states 'List the panels' and 'discover a panel ref' — a query operation with no modification or side effects. The verb 'list' and the purpose of discovery/inspection are characteristic of Read category tools.
Attacks that exploit this kind of access
List the panels (agent/terminal surfaces) in a workspace, so you can discover a panel ref to drive. It is categorised as a Read tool in the Cmux MCP Server, which means it retrieves data without modifying state.
Register the Cmux MCP server in PolicyLayer and add a rule for cmux_list_panels: 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 Cmux. Nothing to install.
cmux_list_panels 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 cmux_list_panels 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 cmux_list_panels. 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.
cmux_list_panels is provided by the Cmux MCP server (puchkoff/cmux-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 →