Get comprehensive package metadata
AI agents call get_package_info 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 retrieves informational data about npm packages (metadata) without side effects. It aligns with the Read category pattern of fetching/querying data. No evidence of code execution, data modification, deletion, or financial operations. Severity is low as misuse would only expose public package information already available through npm registries.
From the tool's definition Tool name 'get_package_info' retrieves 'comprehensive package metadata' with no modification, deletion, or execution capabilities described. Server explicitly focuses on querying and exploring npm packages.
Attacks that exploit this kind of access
Get comprehensive package metadata. 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_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 Context Agent MCP. Nothing to install.
get_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 get_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 get_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.
get_package_info 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 →