runBestPracticesAudit · BrowserTools MCP: Risk & Policy

WHAT IT DOES

What runBestPracticesAudit does on BrowserTools MCP

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

While the tool itself does not modify page state or delete data, it executes an audit process that analyzes the current page. This is execution of a defined operation triggered by the AI agent, fitting the Execute category. Severity is medium because an audit has limited blast radius—it analyzes but does not modify or destroy.

From the tool's definition Tool name 'runBestPracticesAudit' and description 'Run a best practices audit on the current page' indicate execution of an audit operation that analyzes and potentially triggers evaluation logic on live web page content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runBestPracticesAudit Rate-limited

runBestPracticesAudit 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": {
    "runBestPracticesAudit": {
      "limits": [
        {
          "counter": "runbestpracticesaudit_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 runBestPracticesAudit

What does the runBestPracticesAudit tool do? +

Run a best practices audit on the current page. 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 runBestPracticesAudit? +

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

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

Can I rate-limit runBestPracticesAudit? +

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

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

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