Create a new workspace. Returns the workspace_ref so you can use it immediately without a follow-up list call.
AI agents use cmux_new_workspace to create or update resources in Cmux Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cmux Agent environment.
This tool creates a new workspace resource, which is a reversible write operation. It does not execute code, delete data, or involve financial transactions. The blast radius is medium since misuse could create unwanted workspaces but these can typically be cleaned up.
From the tool's definition "Create a new workspace. Returns the workspace_ref so you can use it immediately without a follow-up list call."
Documented attack patterns abuse exactly the kind of access cmux_new_workspace 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_new_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"cmux_new_workspace": {
"limits": [
{
"counter": "cmux_new_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cmux_new_workspace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new workspace. Returns the workspace_ref so you can use it immediately without a follow-up list call. It is categorised as a Write tool in the Cmux Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cmux Agent MCP server in PolicyLayer and add a rule for cmux_new_workspace: 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_new_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cmux_new_workspace 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_new_workspace. 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_new_workspace 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.