Analyze project dependencies (provide either cwd path or package.json content)
AI agents call analyze_dependencies to retrieve information from Npmplus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of dependency metadata—examining what dependencies exist, their versions, and relationships. It retrieves and reports information without creating, modifying, executing code, or destructively removing data. The tool fits the Read category as it queries project structure for informational purposes.
From the tool's definition Tool analyzes and queries dependency information from package.json without modifying, executing, or deleting any data. Description specifies 'analyze' and accepts input parameters (cwd path or package.json content) for inspection only.
Documented attack patterns abuse exactly the kind of access analyze_dependencies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Npmplus, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_dependencies:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_dependencies": {}
}
}analyze_dependencies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze project dependencies (provide either cwd path or package.json content). It is categorised as a Read tool in the Npmplus MCP Server, which means it retrieves data without modifying state.
Register the Npmplus MCP server in PolicyLayer and add a rule for analyze_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 Npmplus. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_dependencies is provided by the Npmplus MCP server (shacharsol/js-package-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Npmplus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Npmplus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.