registry.pypi-lookup

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.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/registry.pypi-lookup.md

WHAT IT DOES

What registry.pypi-lookup does on Mcp

AI agents call registry.pypi-lookup to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why registry.pypi-lookup is rated Low

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

RECOMMENDED RULE

The rule that runs registry.pypi-lookup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For registry.pypi-lookup, this is the rule to start with:

registry.pypi-lookup Allowed

registry.pypi-lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "registry.pypi-lookup": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every registry.pypi-lookup call is checked against it from then on.

FAQ

Questions about registry.pypi-lookup

What does the registry.pypi-lookup tool do? +

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.

How do I enforce a policy on registry.pypi-lookup? +

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.

What risk level is registry.pypi-lookup? +

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

Can I rate-limit registry.pypi-lookup? +

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.

How do I block registry.pypi-lookup completely? +

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.

What MCP server provides registry.pypi-lookup? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →