runNextJSAudit · BrowserTools MCP: Risk & Policy

WHAT IT DOES

What runNextJSAudit does on BrowserTools MCP

AI agents invoke runNextJSAudit to trigger actions in BrowserTools MCP. 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 runNextJSAudit needs a policy

The 'run' prefix and audit context classify this as Execute rather than Read—it triggers an active operation (audit analysis) whose side effects depend on the browser state and audit implementation. It is not Destructive (no deletion/overwriting), Write (no data modification), or Financial.

From the tool's definition Tool name 'runNextJSAudit' indicates execution of an audit operation. The description is empty, but context from sibling tools (runAccessibilityAudit, runAuditMode, runPerformanceAudit, runDebuggerMode) establishes this as a browser analysis/audit tool that…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runNextJSAudit Rate-limited

runNextJSAudit 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": {
    "runNextJSAudit": {
      "limits": [
        {
          "counter": "runnextjsaudit_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 BrowserTools MCP, so you can run agents against it safely.

FAQ

Questions about runNextJSAudit

What does the runNextJSAudit tool do? +

runNextJSAudit. It is categorised as a Execute tool in the BrowserTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on runNextJSAudit? +

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

What risk level is runNextJSAudit? +

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

Can I rate-limit runNextJSAudit? +

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

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

runNextJSAudit is provided by the BrowserTools MCP server (sugatraj/cursor-browser-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.