seopass_lighthouse_plan

Build the heavier Lighthouse execution plan for a SEOPass target URL. seopass_run already emits a lightweight live-readonly verdict.

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/seopass-lighthouse-plan.md

WHAT IT DOES

What seopass_lighthouse_plan does on UnClick

AI agents use seopass_lighthouse_plan to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

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.

RISK

Why seopass_lighthouse_plan is rated Medium

An AI agent can call seopass_lighthouse_plan faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seopass_lighthouse_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seopass_lighthouse_plan, this is the rule to start with:

seopass_lighthouse_plan Rate-limited

seopass_lighthouse_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "seopass_lighthouse_plan": {
      "limits": [
        {
          "counter": "seopass_lighthouse_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every seopass_lighthouse_plan call is checked against it from then on.

FAQ

Questions about seopass_lighthouse_plan

What does the seopass_lighthouse_plan tool do? +

Build the heavier Lighthouse execution plan for a SEOPass target URL. seopass_run already emits a lightweight live-readonly verdict. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does seopass_lighthouse_plan accept? +

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.

How do I enforce a policy on seopass_lighthouse_plan? +

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.

What risk level is seopass_lighthouse_plan? +

seopass_lighthouse_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit seopass_lighthouse_plan? +

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.

How do I block seopass_lighthouse_plan completely? +

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.

What MCP server provides seopass_lighthouse_plan? +

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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

emit_variant_plan on 0sec →team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →