run_flow

Runs the flow with the provided input

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/run-flow.md

WHAT IT DOES

What run_flow does on Genkit MCP

AI agents invoke run_flow 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 run_flow is rated High

This tool executes code or workflows ('runs the flow') whose side effects depend entirely on the input arguments and the flow definition. It does not merely read or write data reversibly—it triggers external operations whose consequences cannot be predicted without knowing the flow contents. This is classic Execute category behavior.

From the tool's definition Tool name 'run_flow' combined with description 'Runs the flow with the provided input' indicates execution of arbitrary flows based on user-supplied input.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_flow 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 run_flow, this is the rule to start with:

run_flow Rate-limited

run_flow 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": {
    "run_flow": {
      "limits": [
        {
          "counter": "run_flow_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 run_flow call is checked against it from then on.

FAQ

Questions about run_flow

What does the run_flow tool do? +

Runs the flow with the provided input. 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 run_flow? +

Register the Genkit MCP server in PolicyLayer and add a rule for run_flow: 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 run_flow? +

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

Can I rate-limit run_flow? +

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

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

run_flow 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

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →