crewai_define_task · CrewAI MCP Orchestrator MCP

WHAT IT DOES

What crewai_define_task does on CrewAI MCP Orchestrator

AI agents use crewai_define_task to create or update resources in CrewAI MCP Orchestrator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CrewAI MCP Orchestrator environment.

WHY IT NEEDS A POLICY

Why crewai_define_task needs a policy

The tool appears to define tasks within a CrewAI system, which is a write operation (creates or modifies task definitions). While the description is empty, the context from the server's purpose (dynamically generate, edit, test, and execute multi-agent systems) and naming patterns of sibling tools strongly suggest task creation/modification.

From the tool's definition Tool name 'crewai_define_task' indicates creation or configuration of a task definition within the CrewAI orchestration framework.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crewai_define_task Rate-limited

crewai_define_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_define_task": {
      "limits": [
        {
          "counter": "crewai_define_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_define_task

What does the crewai_define_task tool do? +

crewai_define_task. It is categorised as a Write tool in the CrewAI MCP Orchestrator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crewai_define_task? +

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

crewai_define_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crewai_define_task? +

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

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

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