Low Risk

get_package_info

get_package_info

How to control get_package_info ↓

What get_package_info does on PyPI Query MCP Server

AI agents call get_package_info to retrieve information from PyPI Query MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_package_info needs a policy

This tool retrieves package metadata from PyPI without modifying, executing code, or causing side effects. Despite the empty description, the naming convention ('get_*'), server purpose ('querying'), and sibling tools (all read-only queries like 'get_download_statistics', 'get_package_dependencies') establish this as a Read operation with low severity—PyPI is a public repository and package metadata is non-sensitive…

From the tool's definition Tool named 'get_package_info' on a PyPI Query server with sibling tools focused on querying package information (dependencies, versions, statistics).

Documented attack patterns abuse exactly the kind of access get_package_info gives an agent:

How to control get_package_info

PolicyLayer is an MCP gateway — it sits between your AI agents and PyPI Query MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_package_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_package_info": {}
  }
}

get_package_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PyPI Query MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_package_info

What does the get_package_info tool do? +

get_package_info. It is categorised as a Read tool in the PyPI Query MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_package_info? +

Register the PyPI Query 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 Query MCP Server. Nothing to install.

What risk level is get_package_info? +

get_package_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_package_info? +

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.

How do I block get_package_info completely? +

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.

What MCP server provides get_package_info? +

get_package_info is provided by the PyPI Query MCP Server MCP server (loonghao/pypi-query-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PyPI Query MCP Server tool call.

Start from PyPI Query MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 PyPI Query MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.