delegate_to_researcher
Hand a research question to the researcher specialist.
This record as markdown: /tools/firebase-genkit/delegate-to-researcher.md
What delegate_to_researcher does on Genkit MCP
AI agents invoke delegate_to_researcher 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.
Why delegate_to_researcher is rated High
This tool delegates a task to an external specialist agent/process, triggering an external operation whose effects depend on the arguments passed. It's not a simple read (it invokes an external agent), so it falls under Execute. Severity is high because delegating to an AI specialist could trigger a chain of further actions with unpredictable scope and side effects.
From the tool's definition Hand a research question to the researcher specialist
Attacks that exploit this kind of access
The rule that runs delegate_to_researcher 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 delegate_to_researcher, this is the rule to start with:
delegate_to_researcher 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 Genkit MCP, apply this rule, and every delegate_to_researcher call is checked against it from then on.
Questions about delegate_to_researcher
Hand a research question to the researcher specialist. 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.
Register the Genkit MCP server in PolicyLayer and add a rule for delegate_to_researcher: 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.
delegate_to_researcher 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 delegate_to_researcher 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 delegate_to_researcher. 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.
delegate_to_researcher 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.
More on Genkit, and thousands of servers like it.
Across the catalogue