crewai_create_project
AI agents use crewai_create_project 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.
The tool creates new project artifacts as part of a CrewAI multi-agent system orchestration platform. This is a reversible data creation operation (Write category) rather than Read (no queries), Execute (no code execution triggered), Destructive (projects can be deleted/reverted), or Financial.
From the tool's definition Tool name 'crewai_create_project' indicates creation of a new project resource. Sibling tools include 'crewai_define_agent', 'crewai_define_task', 'crewai_edit_crew_py', and 'crewai_kickoff', which collectively establish this as a Write-category operation…
Attacks that exploit this kind of access
crewai_create_project. 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.
Register the CrewAI MCP Orchestrator MCP server in PolicyLayer and add a rule for crewai_create_project: 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.
crewai_create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crewai_create_project 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.
Set action: deny in the PolicyLayer policy for crewai_create_project. 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.
crewai_create_project 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →