crewai_kickoff · CrewAI MCP Orchestrator MCP: Risk & Policy

WHAT IT DOES

What crewai_kickoff does on CrewAI MCP Orchestrator

AI agents invoke crewai_kickoff 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_kickoff needs a policy

In CrewAI, 'kickoff' is the primary method to start a crew's execution, triggering multi-agent workflows. This constitutes executing external operations whose effects depend on arguments. The description is empty, so confidence is reduced, but sibling tools like 'crewai_flow_run' confirm this server executes agent systems.

From the tool's definition Tool name 'crewai_kickoff' on a server described as providing tools to 'dynamically generate, edit, test, and execute multi-agent systems'. The 'kickoff' term is standard CrewAI terminology for launching/running a crew execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crewai_kickoff Rate-limited

crewai_kickoff 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_kickoff": {
      "limits": [
        {
          "counter": "crewai_kickoff_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_kickoff

What does the crewai_kickoff tool do? +

crewai_kickoff. 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_kickoff? +

Register the CrewAI MCP Orchestrator MCP server in PolicyLayer and add a rule for crewai_kickoff: 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_kickoff? +

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

Can I rate-limit crewai_kickoff? +

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

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

crewai_kickoff 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.