List stored Lighthouse reports (Layer 1)
AI agents call l1_list_reports 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 retrieves and enumerates existing Lighthouse reports from storage. It performs data retrieval only, with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal — an attacker could only discover what reports exist, not alter or act upon them. This is a classic Read category operation.
From the tool's definition Tool name contains 'list' and description states 'List stored Lighthouse reports' — a query operation with no side effects. No modification, deletion, execution, or financial impact is possible.
Attacks that exploit this kind of access
List stored Lighthouse reports (Layer 1). 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 l1_list_reports: 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.
l1_list_reports 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 l1_list_reports 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 l1_list_reports. 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.
l1_list_reports 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 →