Critical Risk →

cmux_close_surface

Close a surface (tab).

How to control cmux_close_surface ↓

What cmux_close_surface does on Cmux Agent

AI agents call cmux_close_surface to permanently remove resources in Cmux Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cmux_close_surface needs a policy

Closing a surface/tab is an irreversible action that terminates a running session or workspace. Any unsaved state, running processes, or ongoing work within that tab would be lost. This constitutes an irreversible destruction of the surface and its associated state, warranting a Destructive classification with high severity given the potential blast radius of terminating active AI CLI sessions or browser instances.

From the tool's definition Close a surface (tab)

Documented attack patterns abuse exactly the kind of access cmux_close_surface gives an agent:

How to control cmux_close_surface

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_close_surface:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cmux_close_surface"
  ]
}

cmux_close_surface disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Cmux Agent — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cmux_close_surface

What does the cmux_close_surface tool do? +

Close a surface (tab). It is categorised as a Destructive tool in the Cmux Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cmux_close_surface? +

Register the Cmux Agent MCP server in PolicyLayer and add a rule for cmux_close_surface: 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.

What risk level is cmux_close_surface? +

cmux_close_surface is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cmux_close_surface? +

Yes. Add a rate_limit block to the cmux_close_surface 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.

How do I block cmux_close_surface completely? +

Set action: deny in the PolicyLayer policy for cmux_close_surface. 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.

What MCP server provides cmux_close_surface? +

cmux_close_surface 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.

Enforce policy on every Cmux Agent tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.