Get quality, popularity, and maintenance scores for an npm package from npms.io. Provides detailed metrics including download counts, GitHub stars, test coverage indicators, and release frequency. Args: - package_name (string): The npm package name Returns: Comprehensive scoring breakdown: - Over...
AI agents call npm_package_score 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 public npm package information from npms.io. It performs no writes, deletions, executions, or financial operations. The tool is informational only and supports development workflows by providing metrics to help developers evaluate packages. Low severity because misuse would only result in excessive queries or information gathering with no harmful operational impact.
From the tool's definition Tool retrieves package metrics from npms.io including 'quality, popularity, and maintenance scores' with 'download counts, GitHub stars, test coverage indicators'. No mutations or side effects described. Arguments accept only package_name for querying.
Attacks that exploit this kind of access
Get quality, popularity, and maintenance scores for an npm package from npms.io. Provides detailed metrics including download counts, GitHub stars, test coverage indicators, and release frequency. Args: - package_name (string): The npm package name Returns: Comprehensive scoring breakdown: - Overall score (0-100%) - Quality score: carefulness, tests, health, branding - Popularity: community interest, downloads, dependents - Maintenance: release frequency, commit frequency, open issues - GitHub stats: stars, forks, issues - Download statistics 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_score: 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_score 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_score 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_score. 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_score 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 →