List published versions of an npm package with release dates, sorted by most recent first. Args: - package_name (string): The npm package name - limit (number): Maximum versions to return, 1-100 (default: 20) Returns: Version list with publish dates, dist-tags, and deprecation notices. Includes: ...
AI agents call npm_package_versions to retrieve information from Npm Info without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool that queries npm's public package registry. It performs a read-only operation that returns existing metadata about package versions without creating, modifying, executing, or deleting anything. The blast radius is minimal—incorrect usage simply returns inaccurate historical version information with no side effects.
From the tool's definition Tool retrieves and lists published versions of npm packages with metadata like release dates, dist-tags, and deprecation notices. Described as providing 'information' and 'list published versions' with no modification or execution capabilities.
Attacks that exploit this kind of access
List published versions of an npm package with release dates, sorted by most recent first. Args: - package_name (string): The npm package name - limit (number): Maximum versions to return, 1-100 (default: 20) Returns: Version list with publish dates, dist-tags, and deprecation notices. Includes: - version number and publish date for each version - dist-tags annotation (latest, next, beta, etc.) - deprecation warnings where applicable - total version count Examples: -. It is categorised as a Read tool in the Npm Info MCP Server, which means it retrieves data without modifying state.
Register the Npm Info MCP server in PolicyLayer and add a rule for npm_package_versions: 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 Info. Nothing to install.
npm_package_versions 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_package_versions 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_package_versions. 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_package_versions is provided by the Npm Info MCP server (kongyo2/npm-info). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →