crewai_install_deps · CrewAI MCP Orchestrator MCP

WHAT IT DOES

What crewai_install_deps does on CrewAI MCP Orchestrator

AI agents invoke crewai_install_deps 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_install_deps needs a policy

Installing dependencies typically involves executing shell commands (e.g., pip install, npm install) that run external processes and modify the system environment. This falls under Execute as it triggers external operations. Severity is high because installing arbitrary packages could introduce malicious code or alter the runtime environment significantly.

From the tool's definition Tool name 'crewai_install_deps' — 'install_deps' implies installing dependencies (e.g., running pip install or similar package manager commands).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crewai_install_deps Rate-limited

crewai_install_deps 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_install_deps": {
      "limits": [
        {
          "counter": "crewai_install_deps_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_install_deps

What does the crewai_install_deps tool do? +

crewai_install_deps. 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_install_deps? +

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

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

Can I rate-limit crewai_install_deps? +

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

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

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