install_dependencies
Install all project dependencies
This record as markdown: /tools/agentics-ai-code-mcp/install-dependencies.md
What install_dependencies does on Code MCP Server
AI agents invoke install_dependencies to trigger actions in Code MCP Server. 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 install_dependencies is rated High
Installing dependencies runs package manager commands (e.g., npm install, pip install) which execute external processes, download and execute third-party code, and modify the filesystem. This is an Execute-category action with medium severity as it triggers external operations and could introduce malicious packages if the dependency list is compromised.
From the tool's definition Install all project dependencies
Attacks that exploit this kind of access
The rule that runs install_dependencies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_dependencies, this is the rule to start with:
install_dependencies 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every install_dependencies call is checked against it from then on.
Questions about install_dependencies
Install all project dependencies. It is categorised as a Execute tool in the Code MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for install_dependencies: 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 Code MCP Server. Nothing to install.
install_dependencies 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 install_dependencies 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 install_dependencies. 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.
install_dependencies is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
Across the catalogue