Low Risk

audit_dependencies

Audit dependencies for vulnerabilities (provide either cwd path or package.json content)

How to control audit_dependencies ↓

What audit_dependencies does on Npmplus

AI agents call audit_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.

Low Risk

Why audit_dependencies needs a policy

This tool performs security vulnerability scanning and analysis of project dependencies. While it reads and analyzes sensitive security data, it does not modify packages, install software, execute arbitrary code, delete data, or commit financial transactions.

From the tool's definition Tool description states 'Audit dependencies for vulnerabilities' - auditing is a read-only analysis operation that scans for known security issues without modifying packages or executing external code.

Documented attack patterns abuse exactly the kind of access audit_dependencies gives an agent:

How to control audit_dependencies

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 audit_dependencies:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "audit_dependencies": {}
  }
}

audit_dependencies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Npmplus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about audit_dependencies

What does the audit_dependencies tool do? +

Audit dependencies for vulnerabilities (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.

How do I enforce a policy on audit_dependencies? +

Register the Npmplus MCP server in PolicyLayer and add a rule for audit_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.

What risk level is audit_dependencies? +

audit_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit audit_dependencies? +

Yes. Add a rate_limit block to the audit_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.

How do I block audit_dependencies completely? +

Set action: deny in the PolicyLayer policy for audit_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.

What MCP server provides audit_dependencies? +

audit_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.

Enforce policy on every Npmplus tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.