runAuditMode · BrowserTools MCP: Risk & Policy

WHAT IT DOES

What runAuditMode does on BrowserTools MCP

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

This tool executes audit operations across multiple dimensions (SEO, accessibility, performance). While audits are typically read-like in intent, the 'run' verb and the breadth of analysis triggered (coupled with sibling tools like runPerformanceAudit, runAccessibilityAudit) indicate active execution of code/processes whose side effects depend on the target application's state.

From the tool's definition Tool name contains 'run' and description states 'Run audit mode' — indicates execution of operations that analyze and potentially monitor/modify application state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runAuditMode Rate-limited

runAuditMode 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": {
    "runAuditMode": {
      "limits": [
        {
          "counter": "runauditmode_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 runAuditMode

What does the runAuditMode tool do? +

Run audit mode to optimize our application for SEO, accessibility and performance. 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 runAuditMode? +

Register the BrowserTools MCP server in PolicyLayer and add a rule for runAuditMode: 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 runAuditMode? +

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

Can I rate-limit runAuditMode? +

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

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

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