run_npm_audit · VibeServe MCP: Risk & Policy

WHAT IT DOES

What run_npm_audit does on VibeServe

AI agents invoke run_npm_audit to trigger actions in VibeServe. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_npm_audit needs a policy

This tool executes an npm audit command, which is a subprocess/shell operation. While npm audit itself is primarily informational (Read-like), the 'run' verb combined with npm's flexibility to accept arguments like --fix, --force, or custom registry settings means the actual behavior depends on how an AI agent invokes it. This places it in Execute rather than Read.

From the tool's definition Tool name 'run_npm_audit' and description 'Run npm audit for dependency security' indicates execution of an external npm command with potential side effects depending on arguments (e.g., --fix flags could modify package.json and lock files).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_npm_audit Rate-limited

run_npm_audit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_npm_audit": {
      "limits": [
        {
          "counter": "run_npm_audit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeServe, so you can run agents against it safely.

FAQ

Questions about run_npm_audit

What does the run_npm_audit tool do? +

Run npm audit for dependency security. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_npm_audit? +

Register the VibeServe MCP server in PolicyLayer and add a rule for run_npm_audit: 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 VibeServe. Nothing to install.

What risk level is run_npm_audit? +

run_npm_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_npm_audit? +

Yes. Add a rate_limit block to the run_npm_audit 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 run_npm_audit completely? +

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

run_npm_audit is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.