Query and analyze stored Lighthouse results from the database with interpretation
AI agents call l3_database_query 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 queries existing Lighthouse audit results from storage. While it accesses a database, the description focuses on querying and analyzing—passive read operations without creating, modifying, deleting, or executing code. The 'with interpretation' aspect suggests analytical processing of retrieved data rather than side effects.
From the tool's definition Tool name contains 'query' and description states 'Query and analyze stored Lighthouse results from the database' with 'interpretation'. The verb 'query' combined with 'analyze' and 'from the database' indicates data retrieval without modification.
Attacks that exploit this kind of access
Query and analyze stored Lighthouse results from the database with interpretation. 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 l3_database_query: 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.
l3_database_query 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 l3_database_query 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 l3_database_query. 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.
l3_database_query 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.
l3_database_query is one line of Lighthouse's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →