teammate_teleport

Teleport team to a new context/working directory

SERVERClaude Flow SOURCEclaude-flow

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/teammate-teleport.md

WHAT IT DOES

What teammate_teleport does on Claude Flow

AI agents invoke teammate_teleport to trigger actions in Claude Flow. 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.

RISK

Why teammate_teleport is rated High

Changing the working directory or operational context for an agent team triggers an external state transition that affects subsequent operations. This is an Execute-class action since it alters runtime environment state for potentially many agents simultaneously.

From the tool's definition 'Teleport team to a new context/working directory' — changes the working directory/context for a team of agents

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teammate_teleport safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teammate_teleport, this is the rule to start with:

teammate_teleport Rate-limited

teammate_teleport 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": {
    "teammate_teleport": {
      "limits": [
        {
          "counter": "teammate_teleport_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every teammate_teleport call is checked against it from then on.

FAQ

Questions about teammate_teleport

What does the teammate_teleport tool do? +

Teleport team to a new context/working directory. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on teammate_teleport? +

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

What risk level is teammate_teleport? +

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

Can I rate-limit teammate_teleport? +

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

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

teammate_teleport is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →