team_wake_all · Iris MCP: Risk & Policy

WHAT IT DOES

What team_wake_all does on Iris MCP

AI agents invoke team_wake_all to trigger actions in Iris MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why team_wake_all needs a policy

This tool triggers an external operation (waking/activating all teams) across multiple project instances. It is not merely reading data — it initiates active sessions or processes for all configured teams simultaneously.

From the tool's definition 'Wake up all configured teams sequentially. Sounds the air-raid siren and brings all teams online.'

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

team_wake_all Rate-limited

team_wake_all stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "team_wake_all": {
      "limits": [
        {
          "counter": "team_wake_all_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Iris MCP, so you can run agents against it safely.

FAQ

Questions about team_wake_all

What does the team_wake_all tool do? +

Wake up all configured teams sequentially. Sounds the air-raid siren and brings all teams online. It is categorised as a Execute tool in the Iris MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on team_wake_all? +

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

What risk level is team_wake_all? +

team_wake_all is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit team_wake_all? +

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

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

team_wake_all is provided by the Iris MCP server (jenova-marie/iris-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.