List all packages installed in the shared Python environment.
AI agents call list_python_packages to retrieve information from Pwno without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate installed Python packages. It has no capability to modify, delete, or execute code. While the broader server context involves debugging and exploit workflows (high-risk activities), this specific tool is isolated to information retrieval. The low severity reflects minimal blast radius—listing packages cannot compromise systems or data directly.
From the tool's definition Tool name 'list_python_packages' and description 'List all packages installed in the shared Python environment' indicates a query/list operation that retrieves information without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_python_packages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for list_python_packages:
{
"version": "1",
"default": "deny",
"tools": {
"list_python_packages": {}
}
} list_python_packages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all packages installed in the shared Python environment. It is categorised as a Read tool in the Pwno MCP Server, which means it retrieves data without modifying state.
Register the Pwno MCP server in PolicyLayer and add a rule for list_python_packages: 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 Pwno. Nothing to install.
list_python_packages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_python_packages 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 list_python_packages. 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.
list_python_packages is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.