Compare performance metrics across multiple sites (Layer 2)
AI agents call l2_site_comparison 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 reads and compares performance metrics from Lighthouse reports across multiple websites. It performs data retrieval and comparative analysis only, with no side effects, data modification, destructive actions, code execution, or financial implications. The action is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool name 'l2_site_comparison' and description 'Compare performance metrics across multiple sites' indicate retrieval and analysis of existing performance data with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare performance metrics across multiple sites (Layer 2). 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_site_comparison: 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_site_comparison 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_site_comparison 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_site_comparison. 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_site_comparison 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 →