uv-install

Runs uv pip install and returns a structured summary of installed packages. WARNING: may execute untrusted code.

SERVERPython SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-pare-python/uv-install.md

WHAT IT DOES

What uv-install does on Python

AI agents invoke uv-install to trigger actions in Python. 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.

Parameter	Type	Required	Description
`path`	string	—	Working directory
`dryRun`	boolean	—	Preview what would be installed without actually installing (--dry-run)
`extras`	array	—	Package extras to install (--extra NAME)
`noDeps`	boolean	—	Do not install package dependencies (--no-deps)
`python`	string	—	Python interpreter version to use (-p VERSION)
`compact`	boolean	—	Prefer compact output
`upgrade`	boolean	—	Upgrade already-installed packages to the newest version (--upgrade)
`editable`	string	—	Path to local package for editable install (-e PATH)
`indexUrl`	string	—	Base URL of the Python Package Index (-i URL)
`packages`	array	—	Packages to install
`reinstall`	boolean	—	Force reinstall of all packages even if already installed (--reinstall)
`constraint`	string	—	Path to constraints file for version pinning (-c FILE)

Parameters from the server's own tool schema.

RISK

Why uv-install is rated High

Installing packages via uv pip install executes package setup scripts and arbitrary code from potentially untrusted sources. The explicit warning about untrusted code execution confirms the Execute classification. The blast radius is high as malicious packages could compromise the environment.

From the tool's definition 'Runs uv pip install', 'WARNING: may execute untrusted code'

Risk signalsAccepts freeform code/query input (python) · Accepts file system path (path) · High parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uv-install safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Python, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uv-install, this is the rule to start with:

uv-install Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "uv-install": {
      "limits": [
        {
          "counter": "uv-install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Python, apply this rule, and every uv-install call is checked against it from then on.

FAQ

Questions about uv-install

What does the uv-install tool do? +

Runs uv pip install and returns a structured summary of installed packages. WARNING: may execute untrusted code. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does uv-install accept? +

uv-install accepts 12 parameters: path, dryRun, extras, noDeps, python, compact, upgrade, editable, indexUrl, packages, reinstall, constraint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on uv-install? +

Register the Python MCP server in PolicyLayer and add a rule for uv-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 Python. Nothing to install.

What risk level is uv-install? +

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

Can I rate-limit uv-install? +

Yes. Add a rate_limit block to the uv-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.

How do I block uv-install completely? +

Set action: deny in the PolicyLayer policy for uv-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.

What MCP server provides uv-install? +

uv-install is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Python, and thousands of servers like it.

This server

All 14 Python tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →