npm_search

Search npm registry.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/npm-search.md

WHAT IT DOES

What npm_search does on Yaver

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

Parameter	Type	Required	Description
`limit`	integer	—
`query`	string	Yes

Parameters from the server's own tool schema.

RISK

Why npm_search is rated Low

The tool performs a read-only search operation against the npm registry. No packages are installed, modified, or executed. The blast radius is minimal—at worst, an AI agent could learn about available packages, which is low-risk information retrieval. This is a standard lookup operation with no side effects.

From the tool's definition Tool name 'npm_search' and description 'Search npm registry' indicates querying/retrieving package information from npm without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs npm_search safely

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

npm_search Allowed

npm_search 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": {
    "npm_search": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every npm_search call is checked against it from then on.

FAQ

Questions about npm_search

What does the npm_search tool do? +

Search npm registry. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does npm_search accept? +

npm_search accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on npm_search? +

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

What risk level is npm_search? +

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

Can I rate-limit npm_search? +

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

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

npm_search is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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