Get quality metrics from npms.io
AI agents call get_package_quality to retrieve information from NPM Context Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns quality assessment data about npm packages without creating, modifying, executing, or deleting anything. It has no side effects beyond reading external data. The action is purely informational and read-only, consistent with other sibling tools like 'get_download_stats' and 'get_package_info' on the same server.
From the tool's definition Tool retrieves 'quality metrics from npms.io' with no modification or execution capability described. It is a data retrieval operation querying a third-party quality metrics service.
Attacks that exploit this kind of access
Get quality metrics from npms.io. It is categorised as a Read tool in the NPM Context Agent MCP MCP Server, which means it retrieves data without modifying state.
Register the NPM Context Agent MCP server in PolicyLayer and add a rule for get_package_quality: 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 Context Agent MCP. Nothing to install.
get_package_quality 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 get_package_quality 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 get_package_quality. 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.
get_package_quality is provided by the NPM Context Agent MCP server (juansebastiangb/npm-context-agent-mcp). 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 →