pip-install
Runs pip install and returns a structured summary of installed packages. WARNING: may execute untrusted code.
This record as markdown: /tools/io-github-dave-london-cargo/pip-install.md
What pip-install does on Cargo
AI agents invoke pip-install to trigger actions in Cargo. 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 pip-install is rated High
pip install executes package installation which runs setup scripts and arbitrary code from packages. The explicit warning about untrusted code execution confirms this is an Execute-category tool with high severity due to potential for arbitrary code execution on the host system.
From the tool's definition 'Runs pip install' and 'WARNING: may execute untrusted code'
Attacks that exploit this kind of access
The rule that runs pip-install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pip-install, this is the rule to start with:
pip-install 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 Cargo, apply this rule, and every pip-install call is checked against it from then on.
Questions about pip-install
Runs pip install and returns a structured summary of installed packages. WARNING: may execute untrusted code. It is categorised as a Execute tool in the Cargo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cargo MCP server in PolicyLayer and add a rule for pip-install: 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 Cargo. Nothing to install.
pip-install 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 pip-install 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 pip-install. 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.
pip-install is provided by the Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cargo, and thousands of servers like it.
Across the catalogue