This record as markdown: /tools/io-github-kivanccakmak-yaver/npm-info.md
What npm_info does on Yaver
AI agents call npm_info 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 |
|---|---|---|---|
package | string | Yes | npm package name |
Parameters from the server's own tool schema.
Why npm_info is rated Low
This tool queries npm registry for package information (version, download stats, description) without modifying data, executing code, or triggering side effects. It is a straightforward data retrieval operation, placing it firmly in the Read category. The low severity reflects minimal blast radius—incorrect package info retrieval causes no system damage or data loss.
From the tool's definition Tool retrieves npm package metadata: 'Get npm package info — version, downloads, description.' These are read-only queries of public package information with no state changes.
Attacks that exploit this kind of access
The rule that runs npm_info 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_info, this is the rule to start with:
npm_info 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 Yaver, apply this rule, and every npm_info call is checked against it from then on.
Questions about npm_info
Get npm package info — version, downloads, description. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
npm_info accepts 1 parameter: package. Required: package. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for npm_info: 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.
npm_info 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 npm_info 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 npm_info. 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.
npm_info 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue