AI agents call registry.pypi-lookup to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against the PyPI registry to retrieve publicly available package metadata. It has no side effects, cannot modify data, and poses minimal security risk if misused by an AI agent—the worst outcome would be retrieving unnecessary or irrelevant package information.
From the tool's definition Tool description states 'Look up a Python package on PyPI. Returns version, summary, project URLs, license, author/maintainer, classifiers, requires-python, runtime deps, recent release dates, yanked versions.' The verbs are passive/retrieval-only: 'look up'…
Attacks that exploit this kind of access
Look up a Python package on PyPI. Returns version, summary, project URLs, license, author/maintainer, classifiers, requires-python, runtime deps, recent release dates, yanked versions. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for registry.pypi-lookup: 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 Mcp. Nothing to install.
registry.pypi-lookup 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 registry.pypi-lookup 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 registry.pypi-lookup. 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.
registry.pypi-lookup is provided by the MCP server (@2sio/mcp). 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 →