Layer 2 - Analyze critical request chains and identify bottlenecks
AI agents call l2_critical_chain_report to retrieve information from Lighthouse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only analysis of website performance data (critical request chains and bottlenecks). It retrieves and interprets performance information without modifying any data, executing code, or triggering external operations. The analysis is observational—examining existing web performance characteristics to provide recommendations. No side effects or state changes occur.
From the tool's definition Tool name contains 'analyze' and description states 'Analyze critical request chains and identify bottlenecks' — purely diagnostic/analytical functions with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Layer 2 - Analyze critical request chains and identify bottlenecks. It is categorised as a Read tool in the Lighthouse MCP MCP Server, which means it retrieves data without modifying state.
Register the Lighthouse MCP server in PolicyLayer and add a rule for l2_critical_chain_report: 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 Lighthouse MCP. Nothing to install.
l2_critical_chain_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the l2_critical_chain_report 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.
Set action: deny in the PolicyLayer policy for l2_critical_chain_report. 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.
l2_critical_chain_report is provided by the Lighthouse MCP server (mizchi/lighthouse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →