This record as markdown: /tools/ruflo/teammate-push-remote.md
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 teammate_push_remote is rated High
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
The rule that runs teammate_push_remote safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teammate_push_remote, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every teammate_push_remote call is checked against it from then on.
Questions about teammate_push_remote
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.
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.
teammate_push_remote is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Ruflo, and thousands of servers like it.
Across the catalogue