pypi.packages.info
Get metadata for any Python package from PyPI: version, summary, license, author, dependencies, classifiers, Python version requirements. 550K+ packages. Supports specific version lookup. Complements npm (UC-344) for polyglot dependency intelligence.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/pypi.packages.info.md
What pypi.packages.info does on Apibase
AI agents call pypi.packages.info to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | Yes | Python package name (e.g. requests, flask, numpy, anthropic) |
version | string | — | Specific version (e.g. 2.31.0). Defaults to latest release. |
Parameters from the server's own tool schema.
Why pypi.packages.info is rated Low
Retrieves public package metadata without side effects; no data modification or code execution.
From the tool's definition Get metadata for any Python package from PyPI: version, summary, license, author, dependencies, classifiers
Attacks that exploit this kind of access
The rule that runs pypi.packages.info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pypi.packages.info, this is the rule to start with:
pypi.packages.info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every pypi.packages.info call is checked against it from then on.
Questions about pypi.packages.info
Get metadata for any Python package from PyPI: version, summary, license, author, dependencies, classifiers, Python version requirements. 550K+ packages. Supports specific version lookup. Complements npm (UC-344) for polyglot dependency intelligence. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
pypi.packages.info accepts 2 parameters: package, version. Required: package. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for pypi.packages.info: 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 Apibase. Nothing to install.
pypi.packages.info 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 pypi.packages.info 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 pypi.packages.info. 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.
pypi.packages.info is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue