AI agents invoke seopass_run to trigger actions in UnClick. 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 | — | Target URL for a one-off SEOPass plan |
pack_name | string | — | Name of a registered SEOPass pack; the pack URL is used as the target |
Parameters from the server's own tool schema.
This tool triggers execution of web crawling and Lighthouse audits against arbitrary URLs. While the description indicates 'Chunk 1 returns...without persisting results', the tool still executes external scanning operations.
From the tool's definition Tool description states 'Plan a SEOPass run against a URL or registered pack' and references 'crawl and Lighthouse execution plan' — this describes automated execution of web crawling and performance auditing operations against external URLs, which are…
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Plan a SEOPass run against a URL or registered pack. Chunk 1 returns the crawl and Lighthouse execution plan without persisting results. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
seopass_run accepts 2 parameters: url, pack_name. 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_run: 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_run 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 seopass_run 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_run. 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_run 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 →