Critical Risk →

close_workers

close_workers

How to control close_workers ↓

What close_workers does on Claude Team MCP Server

AI agents call close_workers to permanently remove resources in Claude Team MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why close_workers needs a policy

The name 'close_workers' strongly implies terminating worker sessions, which would be an irreversible action (closing terminal sessions cannot be undone, and any unsaved state would be lost). Given the server context of managing Claude Code sessions in iTerm2, closing workers likely terminates running processes.

From the tool's definition Tool name 'close_workers' on a server that manages terminal sessions and git worktrees; description is empty

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

How to control close_workers

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Team MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for close_workers:

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

close_workers 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 Claude Team MCP Server — 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 close_workers

What does the close_workers tool do? +

close_workers. It is categorised as a Destructive tool in the Claude Team MCP Server 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 close_workers? +

Register the Claude Team MCP Server MCP server in PolicyLayer and add a rule for close_workers: 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 Team MCP Server. Nothing to install.

What risk level is close_workers? +

close_workers 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 close_workers? +

Yes. Add a rate_limit block to the close_workers 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 close_workers completely? +

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

close_workers is provided by the Claude Team MCP Server MCP server (martian-engineering/maniple). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Team MCP Server tool call.

Start from Claude Team MCP Server, 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.

16 Claude Team MCP Server 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.