Low Risk

list_workers

list_workers

How to control list_workers ↓

What list_workers does on Claude Team MCP Server

AI agents call list_workers to retrieve information from Claude Team MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_workers needs a policy

This tool retrieves information about existing worker sessions. While the description is empty, the name and context from related tools (polling, examining, discovering workers) clearly suggest it queries state without modifying it. The blast radius of misuse is minimal—an agent can only gain visibility into running sessions, not alter or delete them.

From the tool's definition Tool name 'list_workers' combined with sibling tools like 'discover_workers', 'check_idle_workers', and 'examine_worker' indicates query/inspection functionality. The verb 'list' is consistently associated with retrieval operations that have no side effects.

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

How to control list_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 list_workers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_workers": {}
  }
}

list_workers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_workers

What does the list_workers tool do? +

list_workers. It is categorised as a Read tool in the Claude Team MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_workers? +

Register the Claude Team MCP Server MCP server in PolicyLayer and add a rule for list_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 list_workers? +

list_workers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_workers? +

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

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

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