This record as markdown: /tools/io-github-dave-london-pare-search/pm-ls.md
What pm-ls does on Search
AI agents call pm-ls to retrieve information from Search without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pm-ls is rated Low
Package manager list commands are read-only operations that retrieve and display installed packages or package metadata. They have no side effects, reversible changes, or external operations. No data is created, modified, or deleted. The incomplete description lowers confidence slightly, but the 'ls' suffix strongly indicates a listing/read operation.
From the tool's definition Tool name 'pm-ls' suggests a package manager list operation. Description states 'Runs' but is incomplete; however, the naming pattern and context within a search/query server indicate this lists or queries package information without modification.
Attacks that exploit this kind of access
The rule that runs pm-ls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pm-ls, this is the rule to start with:
pm-ls 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 Search, apply this rule, and every pm-ls call is checked against it from then on.
Questions about pm-ls
Runs. It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.
Register the Search MCP server in PolicyLayer and add a rule for pm-ls: 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 Search. Nothing to install.
pm-ls 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 pm-ls 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 pm-ls. 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.
pm-ls is provided by the Search 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 Search, and thousands of servers like it.
This server
Across the catalogue