team_launch · Iris MCP: Risk & Policy

WHAT IT DOES

What team_launch does on Iris MCP

AI agents invoke team_launch 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_launch needs a policy

The tool initiates and manages running processes ('ensuring its process is active'). This is an Execute category action: it triggers external operations whose side effects depend on arguments (which team to launch). While not immediately destructive, process launching in a multi-project coordination system could trigger unintended computational work, resource consumption, or operations in other codebases.

From the tool's definition Tool description states 'Launch a team by ensuring its process is active' - this triggers external process activation/execution whose effects depend on which team is targeted and what that team's process does.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

team_launch Rate-limited

team_launch 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_launch": {
      "limits": [
        {
          "counter": "team_launch_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_launch

What does the team_launch tool do? +

Launch a team by ensuring its process is active. 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_launch? +

Register the Iris MCP server in PolicyLayer and add a rule for team_launch: 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_launch? +

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

Can I rate-limit team_launch? +

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

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

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