teammate_push_remote · Ruflo MCP: Risk & Policy

WHAT IT DOES

What teammate_push_remote does on Ruflo

AI agents invoke teammate_push_remote to trigger actions in Ruflo. 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 teammate_push_remote needs a policy

This tool pushes/deploys an agent team to a remote Claude.ai session, triggering an external operation that creates or initiates a live multi-agent swarm in a remote environment. 'Push' to a remote session implies activating or deploying agents externally, which goes beyond a simple write — it executes or initiates an external workflow.

From the tool's definition Push team to Claude.ai remote session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teammate_push_remote Rate-limited

teammate_push_remote 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_push_remote": {
      "limits": [
        {
          "counter": "teammate_push_remote_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 Ruflo, so you can run agents against it safely.

FAQ

Questions about teammate_push_remote

What does the teammate_push_remote tool do? +

Push team to Claude.ai remote session. It is categorised as a Execute tool in the Ruflo 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_push_remote? +

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

What risk level is teammate_push_remote? +

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

Can I rate-limit teammate_push_remote? +

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

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

teammate_push_remote is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

teammate_push_remote is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →