Get comprehensive information about an npm package including latest version, description, license, homepage, repository, keywords, engines, and maintainers. Args: - package_name (string): The npm package name Returns: Package metadata including: - name, latest version, description - license, home...
AI agents call npm_package_info 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 data retrieval tool that queries the npm registry for publicly available package information. It has no side effects, cannot modify data, cannot execute code, and cannot cause financial impact. The only minor information disclosure risk is if sensitive maintainer contact details were exposed, but npm maintainer information is publicly listed by design.
From the tool's definition Tool retrieves npm package metadata including 'latest version, description, license, homepage, repository, keywords, engines, and maintainers' with no modification capabilities.
Attacks that exploit this kind of access
Get comprehensive information about an npm package including latest version, description, license, homepage, repository, keywords, engines, and maintainers. Args: - package_name (string): The npm package name Returns: Package metadata including: - name, latest version, description - license, homepage, repository URL - keywords, engines (node/npm version requirements) - dist-tags (latest, next, beta, etc.) - maintainers list - author information 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_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 Npm Info. Nothing to install.
npm_package_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_package_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_package_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_package_info 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 →