install_python_package
Install a Python package in a virtual environment on the API server.
This record as markdown: /tools/nyxstrike/install-python-package.md
What install_python_package does on Nyxstrike
AI agents invoke install_python_package to trigger actions in Nyxstrike. 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_python_package is rated High
Installing packages on a remote server executes package manager commands and modifies the server environment. On a penetration testing platform, this could be used to install malicious or offensive tooling. The action runs code/commands server-side and has lasting side effects, placing it in Execute.
From the tool's definition "Install a Python package in a virtual environment on the API server"
Attacks that exploit this kind of access
The rule that runs install_python_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_python_package, this is the rule to start with:
install_python_package 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 Nyxstrike, apply this rule, and every install_python_package call is checked against it from then on.
Questions about install_python_package
Install a Python package in a virtual environment on the API server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for install_python_package: 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 Nyxstrike. Nothing to install.
install_python_package 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_python_package 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_python_package. 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_python_package is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue