pip-show
Runs pip show and returns structured package metadata (name, version, summary, dependencies).
This record as markdown: /tools/io-github-dave-london-git/pip-show.md
What pip-show does on Git
AI agents call pip-show to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pip-show is rated Low
This tool only queries and retrieves existing package metadata. It has no side effects, does not modify system state, and does not execute arbitrary code. It is purely informational, making it a Read operation with low severity risk.
From the tool's definition Tool description states it 'Runs pip show and returns structured package metadata (name, version, summary, dependencies)'. The pip show command retrieves and displays package information without modifying, deleting, or executing code.
Attacks that exploit this kind of access
The rule that runs pip-show safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pip-show, this is the rule to start with:
pip-show 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 Git, apply this rule, and every pip-show call is checked against it from then on.
Questions about pip-show
Runs pip show and returns structured package metadata (name, version, summary, dependencies). It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git MCP server in PolicyLayer and add a rule for pip-show: 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 Git. Nothing to install.
pip-show 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 pip-show 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 pip-show. 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.
pip-show is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue