run_audit_mode · Chromium ARM64 Browser MCP: Risk & Policy

WHAT IT DOES

What run_audit_mode does on Chromium ARM64 Browser

AI agents invoke run_audit_mode 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_audit_mode needs a policy

The tool executes an audit operation on web content within the browser context. While the description is vague, the context of browser automation with JavaScript execution capabilities and integration with sibling tools like 'evaluate' and 'click' indicates this triggers executable operations. The 'audit mode' phrasing suggests it runs automated checks/scans rather than passive data retrieval.

From the tool's definition 'Run comprehensive audit mode for optimization' combined with context that this is a browser automation tool capable of 'JavaScript execution' and 'complete SaaS testing workflows'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_audit_mode Rate-limited

run_audit_mode 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_audit_mode": {
      "limits": [
        {
          "counter": "run_audit_mode_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_audit_mode

What does the run_audit_mode tool do? +

Run comprehensive audit mode for optimization. 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_audit_mode? +

Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for run_audit_mode: 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_audit_mode? +

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

Can I rate-limit run_audit_mode? +

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

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

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