AI agents call seopass_lighthouse_plan to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL to audit with Lighthouse |
strategy | string | — | Lighthouse strategy (default: mobile) |
categories | array | — | Lighthouse categories to request |
Parameters from the server's own tool schema.
The description explicitly states that execution and persistence happen in a later step. This tool only builds/reads a plan structure for a given URL, making it a Read/planning operation with no side effects at this stage.
From the tool's definition 'Build the Lighthouse execution plan for a SEOPass target URL. Execution and persistence land in a later chunk.' — this tool only constructs a plan; it does not execute or persist anything.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Build the Lighthouse execution plan for a SEOPass target URL. Execution and persistence land in a later chunk. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
seopass_lighthouse_plan accepts 3 parameters: url, strategy, categories. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for seopass_lighthouse_plan: 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 UnClick. Nothing to install.
seopass_lighthouse_plan 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 seopass_lighthouse_plan 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 seopass_lighthouse_plan. 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.
seopass_lighthouse_plan is provided by the UnClick MCP server (@unclick/mcp-server). 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 →