Analyze unused CSS and JavaScript (Layer 2)
AI agents call l2_unused_code 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 static analysis of website resources (CSS and JavaScript) to identify unused code. It retrieves and examines data about a website's code usage patterns and returns insights. This is a read-only operation with no side effects, modifications, or external code execution. The tool does not create, modify, or delete data; it only analyzes and reports findings.
From the tool's definition Tool name is 'l2_unused_code' with description 'Analyze unused CSS and JavaScript (Layer 2)'. The verb 'analyze' combined with the Lighthouse context indicates this tool queries and reports on website code metrics without modifying, executing, or deleting…
Attacks that exploit this kind of access
Analyze unused CSS and JavaScript (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_unused_code: 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_unused_code 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_unused_code 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_unused_code. 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_unused_code 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 →