crewai_flow_run · CrewAI MCP Orchestrator MCP: Risk & Policy

WHAT IT DOES

What crewai_flow_run does on CrewAI MCP Orchestrator

AI agents invoke crewai_flow_run to trigger actions in CrewAI MCP Orchestrator. 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 IT NEEDS A POLICY

Why crewai_flow_run needs a policy

Executing a CrewAI flow runs arbitrary multi-agent workflows that can perform read/write/external operations. The blast radius is high because a compromised flow definition could interact with external systems, modify data, or execute unintended actions across multiple agents.

From the tool's definition Tool name 'crewai_flow_run' indicates execution of a CrewAI workflow/flow. The server enables 'dynamically generate, edit, test, and execute multi-agent systems.' No description provided, but contextual pattern with sibling tools (crewai_kickoff,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crewai_flow_run Rate-limited

crewai_flow_run 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": {
    "crewai_flow_run": {
      "limits": [
        {
          "counter": "crewai_flow_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CrewAI MCP Orchestrator, so you can run agents against it safely.

FAQ

Questions about crewai_flow_run

What does the crewai_flow_run tool do? +

crewai_flow_run. It is categorised as a Execute tool in the CrewAI MCP Orchestrator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on crewai_flow_run? +

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

What risk level is crewai_flow_run? +

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

Can I rate-limit crewai_flow_run? +

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

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

crewai_flow_run is provided by the CrewAI MCP Orchestrator MCP server (ssolis-ti/crewai-mcp-hq). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.