crewai_train_crew
AI agents invoke crewai_train_crew 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.
Based on the tool name, this likely executes a training run for a CrewAI crew, which involves running computational processes and potentially modifying model state. Training operations typically have significant side effects (resource consumption, model modification). However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'crewai_train_crew' suggests training a CrewAI crew, which would involve executing a training process; description is empty and uninformative.
Attacks that exploit this kind of access
crewai_train_crew. 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.
Register the CrewAI MCP Orchestrator MCP server in PolicyLayer and add a rule for crewai_train_crew: 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_train_crew is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crewai_train_crew 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_train_crew. 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_train_crew 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 →