Low Risk

search_npm

Search for npm packages

How to control search_npm ↓

What search_npm does on NPM Helper MCP

AI agents call search_npm to retrieve information from NPM Helper MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_npm needs a policy

This tool retrieves package information from the NPM registry without creating, modifying, deleting, or executing anything. It is a straightforward read operation analogous to searching a database or listing results. The broader server context (dependency management) does not alter this classification for this specific tool.

From the tool's definition Tool name is 'search_npm' and description states 'Search for npm packages' — a query operation with no side effects.

Documented attack patterns abuse exactly the kind of access search_npm gives an agent:

How to control search_npm

PolicyLayer is an MCP gateway — it sits between your AI agents and NPM Helper MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_npm:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_npm": {}
  }
}

search_npm is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NPM Helper MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_npm

What does the search_npm tool do? +

Search for npm packages. It is categorised as a Read tool in the NPM Helper MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_npm? +

Register the NPM Helper MCP server in PolicyLayer and add a rule for search_npm: 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 Helper MCP. Nothing to install.

What risk level is search_npm? +

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

Can I rate-limit search_npm? +

Yes. Add a rate_limit block to the search_npm 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 search_npm completely? +

Set action: deny in the PolicyLayer policy for search_npm. 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 search_npm? +

search_npm is provided by the NPM Helper MCP server (pinkpixel-dev/npm-helper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NPM Helper MCP tool call.

Start from NPM Helper MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 NPM Helper MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.