lighthouse_audit
Run Lighthouse checks
Part of the Chrome DevTools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call lighthouse_audit to retrieve information from Chrome DevTools without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON LIGHTHOUSE_AUDIT
Even though lighthouse_audit only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
lighthouse_audit:
rules:
- action: allowSee the full Chrome DevTools policy for all 29 tools.
DETAILS
MORE CHROME DEVTOOLS TOOLS
list_pages Read take_screenshot Read take_snapshot Read list_console_messages Read get_console_message Read list_network_requests Read get_network_request Read take_memory_snapshot Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the lighthouse_audit tool do?
Run Lighthouse checks. It is categorised as a Read tool in the Chrome DevTools MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on lighthouse_audit?
Add a rule in your Intercept YAML policy under the tools section for lighthouse_audit. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome DevTools MCP server.
What risk level is lighthouse_audit?
lighthouse_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit lighthouse_audit?
Yes. Add a rate_limit block to the lighthouse_audit rule in your Intercept 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 lighthouse_audit completely?
Set action: deny in the Intercept policy for lighthouse_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 lighthouse_audit?
lighthouse_audit is provided by the Chrome DevTools MCP server (ChromeDevTools/chrome-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON CHROME DEVTOOLS
Open source. One binary. Zero dependencies.