Show context info for the current CMUX session — focused window, workspace, pane, surface refs. Call this first to discover IDs for other tools.
AI agents call cmux_identify to retrieve information from Cmux Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information-retrieval tool that queries the current state of a CMUX session and returns context data. It has no side effects, does not modify state, and serves only to read and expose session identifiers and metadata. This is a Read category operation with low severity and low blast radius — misuse would only expose information, not cause operational harm.
From the tool's definition Tool name 'cmux_identify' and description 'Show context info for the current CMUX session' — retrieves and displays session metadata without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access cmux_identify gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cmux Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for cmux_identify:
{
"version": "1",
"default": "deny",
"tools": {
"cmux_identify": {}
}
} cmux_identify is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show context info for the current CMUX session — focused window, workspace, pane, surface refs. Call this first to discover IDs for other tools. It is categorised as a Read tool in the Cmux Agent MCP Server, which means it retrieves data without modifying state.
Register the Cmux Agent MCP server in PolicyLayer and add a rule for cmux_identify: 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 Agent. Nothing to install.
cmux_identify 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_identify 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_identify. 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_identify is provided by the Cmux Agent MCP server (multiagentcognition/cmux-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cmux Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
63 Cmux Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.