Controlling coding agent dependency installs with ToolPolicy and egress allowlists
HowDevelop · x · 2026-10-04
To mitigate supply-chain risk when coding agents autonomously run npm install or pip install:
- Apply a ToolPolicy to the agent's shell tool (e.g. Bash), evaluating command arguments against CEL rules and enforcing them.
- Layer an egress allowlist restricting downloads to an approved internal package mirror or proxy — but the mirror's approval process matters too; allowing a registry doesn't make every package inside it safe.
- Mind the boundary: ArtifactPolicy governs OCI artifacts (agent definitions, MCP servers, skills, policy bundles); npm/PyPI installs fall under ToolPolicy.
- Key pattern: control both the installation action and the source it downloads from.
More from coding & agent
- Railway launches Cloud Agent Tasks: machine, conversation and result are separate — reusing a VM doesn't mean memory — krishnan · 2026-11-20
- Eric Schmidt: founding an agentic AI company is the easiest way to get rich in the next two years — AICopyLab · 2026-11-20
- Apple reportedly building proactive AI agent that acts autonomously on users' behalf — burny_tech · 2026-11-20
- NormGym benchmark shows agents learn from own norm violations but not from others — xuanalogue · 2026-11-20
- Every adopted 'compound engineering' company-wide so its codebase gets easier to maintain — every · 2026-11-20
- Not every agent task needs a general LLM — specialized small models by task type — ziv_ravid · 2026-11-20