run_nextjs_audit · Chromium ARM64 Browser MCP: Risk & Policy

WHAT IT DOES

What run_nextjs_audit does on Chromium ARM64 Browser

AI agents invoke run_nextjs_audit to trigger actions in Chromium ARM64 Browser. 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_nextjs_audit needs a policy

This tool executes a Next.js-specific audit, which involves running diagnostic code/scripts against a web page to analyze its framework-specific properties and state. While audits are non-destructive information-gathering operations, the act of executing code against a page (particularly framework-specific diagnostic code) falls under Execute rather than Read, as the effects depend on the page's configuration and…

From the tool's definition Tool name 'run_nextjs_audit' combined with server description indicating 'JavaScript execution' and 'SaaS testing workflows'; audit operations typically execute diagnostic code against the target page to analyze its state, dependencies, and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_nextjs_audit Rate-limited

run_nextjs_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_nextjs_audit": {
      "limits": [
        {
          "counter": "run_nextjs_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 Chromium ARM64 Browser, so you can run agents against it safely.

FAQ

Questions about run_nextjs_audit

What does the run_nextjs_audit tool do? +

Run a Next.js specific audit on the current page. It is categorised as a Execute tool in the Chromium ARM64 Browser 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_nextjs_audit? +

Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for run_nextjs_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 Chromium ARM64 Browser. Nothing to install.

What risk level is run_nextjs_audit? +

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

Can I rate-limit run_nextjs_audit? +

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

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

run_nextjs_audit is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.