transferToAgent

Call this to transfer conversation control to a different specialist agent.

SERVERGenkit MCP SOURCEgenkit-ai/genkit

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/firebase-genkit/transfertoagent.md

WHAT IT DOES

What transferToAgent does on Genkit MCP

AI agents invoke transferToAgent to trigger actions in Genkit 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.

RISK

Why transferToAgent is rated High

This tool triggers an external operation — routing/transferring control to another agent — whose effects depend on which agent is targeted. It is not a simple read or write; it executes a handoff that could cause a different AI agent to take over and perform arbitrary downstream actions, making misuse potentially high-impact.

From the tool's definition "transfer conversation control to a different specialist agent"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transferToAgent safely

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

transferToAgent Rate-limited

transferToAgent 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": {
    "transferToAgent": {
      "limits": [
        {
          "counter": "transfertoagent_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 Genkit MCP, apply this rule, and every transferToAgent call is checked against it from then on.

FAQ

Questions about transferToAgent

What does the transferToAgent tool do? +

Call this to transfer conversation control to a different specialist agent. It is categorised as a Execute tool in the Genkit 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 transferToAgent? +

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

What risk level is transferToAgent? +

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

Can I rate-limit transferToAgent? +

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

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

transferToAgent is provided by the Genkit MCP server (genkit-ai/genkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genkit, and thousands of servers like it.

This server

All 72 Genkit 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 →