This record as markdown: /tools/com-geekflare-mcp/lighthouse.md
What lighthouse does on Mcp
AI agents invoke lighthouse to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL |
device | string | — | |
parameters | array | — | Extra Lighthouse CLI parameters |
proxyCountry | string | — | Country code for proxy routing |
followRedirect | boolean | — |
Parameters from the server's own tool schema.
Why lighthouse is rated High
This tool triggers an external operation (Lighthouse audit) whose side effects depend on the target website argument. While it does not modify data or execute arbitrary code on the user's system, it runs a complex automated inspection process on remote targets that could be resource-intensive, potentially cause rate-limiting issues, or trigger security alerts on the target server.
From the tool's definition "Run Lighthouse audit on a website" — Lighthouse is a tool that executes audits, which involves automated inspection and analysis of web pages, requiring the tool to fetch, render, and analyze remote content.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs lighthouse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lighthouse, this is the rule to start with:
lighthouse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every lighthouse call is checked against it from then on.
Questions about lighthouse
Run Lighthouse audit on a website. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
lighthouse accepts 5 parameters: url, device, parameters, proxyCountry, followRedirect. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for lighthouse: 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 Mcp. Nothing to install.
lighthouse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lighthouse 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 lighthouse. 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.
lighthouse is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue