Get dependency information for a specific version of an npm package. By default returns direct dependencies of all kinds (dependencies, devDependencies, peerDependencies, optionalDependencies) along with totals. When \
AI agents call npm_package_dependencies 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 tool retrieves and queries npm package metadata (dependency lists) for a specific package version. It has no side effects—it does not create, modify, delete, or execute code. It is a pure information lookup operation similar to the other sibling tools on this server (npm_package_info, npm_package_readme, etc.).
From the tool's definition Tool returns dependency information for npm packages without modifying, deleting, or executing anything. Description states 'Get dependency information' and lists what it 'returns' (direct dependencies, totals), indicating a read-only query operation.
Attacks that exploit this kind of access
Get dependency information for a specific version of an npm package. By default returns direct dependencies of all kinds (dependencies, devDependencies, peerDependencies, optionalDependencies) along with totals. When \. 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_dependencies: 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_dependencies 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_dependencies 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_dependencies. 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_dependencies 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 →