worker_events

THE RISK

Low Risk

Why worker_events needs a policy

With no description available, the tool's behavior cannot be determined from available information. The name 'worker_events' suggests it may retrieve or monitor events related to worker sessions (which would be Read), but without a description, confidence is very low.

From the tool's definition Tool description is empty and uninformative; name 'worker_events' alone is ambiguous

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

POLICY

How to control worker_events

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "worker_events": {
      "limits": [
        {
          "counter": "worker_events_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

worker_events gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Claude Team MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Team MCP Server tools

Destructive prune_recovered_workers prune_recovered_workers Destructive close_workers close_workers Execute wait_idle_workers wait_idle_workers Execute message_workers message_workers Execute spawn_workers spawn_workers Other adopt_worker adopt_worker Read check_idle_workers check_idle_workers Read discover_workers discover_workers

All 16 Claude Team MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about worker_events

What does the worker_events tool do? +

worker_events. It is categorised as a Other tool in the Claude Team MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on worker_events? +

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

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

Can I rate-limit worker_events? +

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

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

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

CHECK YOUR STACK →