pip-audit
Runs pip-audit and returns a structured vulnerability report.
This record as markdown: /tools/io-github-dave-london-pare-test/pip-audit.md
What pip-audit does on Test
AI agents invoke pip-audit to trigger actions in Test. 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-audit is rated High
The tool executes the pip-audit command-line tool against the environment and returns results. This constitutes running an external program. While pip-audit is read-only in intent (scanning for vulnerabilities), it executes a subprocess whose behavior depends on the environment. No data is modified or deleted, but the execution of external commands places it in the Execute category.
From the tool's definition "Runs pip-audit" — explicitly runs an external tool/command
Attacks that exploit this kind of access
The rule that runs pip-audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pip-audit, this is the rule to start with:
pip-audit 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 Test, apply this rule, and every pip-audit call is checked against it from then on.
Questions about pip-audit
Runs pip-audit and returns a structured vulnerability report. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for pip-audit: 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 Test. Nothing to install.
pip-audit 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-audit 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-audit. 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-audit is provided by the Test 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 Test, and thousands of servers like it.
This server
Across the catalogue