run_accessibility_audit · Chromium ARM64 Browser MCP

WHAT IT DOES

What run_accessibility_audit does on Chromium ARM64 Browser

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

Running an accessibility audit executes automated scanning code whose behavior depends on the current page state (argument). While non-destructive, it qualifies as Execute rather than Read because it actively triggers external analysis operations and may trigger side effects (e.g., page traversal, JavaScript injection for instrumentation).

From the tool's definition Tool performs 'Run an accessibility audit on the current page' — this executes a third-party audit tool against the current DOM/page state, triggering code execution that scans and analyzes page content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_accessibility_audit Rate-limited

run_accessibility_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_accessibility_audit": {
      "limits": [
        {
          "counter": "run_accessibility_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_accessibility_audit

What does the run_accessibility_audit tool do? +

Run an accessibility 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_accessibility_audit? +

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

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

Can I rate-limit run_accessibility_audit? +

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

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

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