New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delegate_to_researcher

Hand a research question to the researcher specialist.

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/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

Questions about delegate_to_researcher

What does the delegate_to_researcher tool do? +

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.

How do I enforce a policy on delegate_to_researcher? +

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.

What risk level is delegate_to_researcher? +

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

Can I rate-limit delegate_to_researcher? +

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.

How do I block delegate_to_researcher completely? +

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.

What MCP server provides delegate_to_researcher? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Genkit's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.