This record as markdown: /tools/io-github-dave-london-npm/pm-ls.md
What pm-ls does on Npm
AI agents call pm-ls to retrieve information from Npm 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
This tool appears to be a package manager list command (equivalent to 'npm ls' or 'pnpm ls'), which retrieves and displays dependency trees or package information without modifying, executing, or deleting anything. The incomplete description lowers confidence slightly, but the naming convention and server context strongly suggest a read-only operation.
From the tool's definition Tool name 'pm-ls' and context of npm/pnpm operations suggest it lists package information. Description is incomplete ('Runs') but the tool name and server description ('list' operations as typed JSON) indicate a read-only query operation.
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 Npm, 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 Npm, 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 Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm 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 Npm. 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 Npm 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 Npm, and thousands of servers like it.
This server
Across the catalogue