Low Risk

examine_worker

examine_worker

How to control examine_worker ↓

What examine_worker does on Claude Team MCP Server

AI agents call examine_worker 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 examine_worker needs a policy

The name 'examine_worker' implies reading or inspecting the state of a worker session (consistent with sibling tools like 'list_workers', 'check_idle_workers', 'discover_workers' which are read-oriented monitoring tools). However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'examine_worker' suggests inspection/monitoring of a worker session; description is empty and uninformative.

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

How to control examine_worker

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

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

examine_worker 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 examine_worker

What does the examine_worker tool do? +

examine_worker. 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 examine_worker? +

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

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

Can I rate-limit examine_worker? +

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

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

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