Get detailed information about a Python package.
AI agents call get_package_info to retrieve information from PyPI Package MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries package information from PyPI without creating, modifying, deleting, executing code, or performing financial transactions. It is a read-only operation with no side effects. Severity is low because misuse would only expose publicly available metadata.
From the tool's definition Tool name 'get_package_info' and description 'Get detailed information about a Python package' indicate retrieval of package metadata without modification. The server context emphasizes 'fetch, explore, and analyze' operations.
Attacks that exploit this kind of access
Get detailed information about a Python package. It is categorised as a Read tool in the PyPI Package MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PyPI Package MCP Server MCP server in PolicyLayer and add a rule for get_package_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 PyPI Package MCP Server. Nothing to install.
get_package_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 get_package_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 get_package_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.
get_package_info is provided by the PyPI Package MCP Server MCP server (qvakk/python-package-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →