seopass_run

Run SEOPass against a public URL or registered pack. Returns a live-readonly SEO verdict, score, findings, fix prompts, and an in-session run id.

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 30 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-run.md

WHAT IT DOES

What seopass_run does on UnClick

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 read-only run
`pack_name`	string	—	Name of a registered SEOPass pack; the pack URL is used as the target
`target_sha`	string	—	Optional PR or commit SHA for receipt staleness checks

Parameters from the server's own tool schema.

RISK

Why seopass_run is rated High

This tool executes an external SEO analysis service against user-supplied URLs. While the results are read-only and the operation itself is non-destructive, it constitutes execution of an external operation whose effects and scope depend on the URL argument provided.

From the tool's definition Tool name 'seopass_run' combined with description 'Run SEOPass against a public URL' indicates execution of an external SEO analysis operation.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seopass_run 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_run, this is the rule to start with:

seopass_run Rate-limited

seopass_run 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "seopass_run": {
      "limits": [
        {
          "counter": "seopass_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_run call is checked against it from then on.

FAQ

Questions about seopass_run

What does the seopass_run tool do? +

Run SEOPass against a public URL or registered pack. Returns a live-readonly SEO verdict, score, findings, fix prompts, and an in-session run id. 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.

What parameters does seopass_run accept? +

seopass_run accepts 3 parameters: url, pack_name, target_sha. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on seopass_run? +

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.

What risk level is seopass_run? +

seopass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit seopass_run? +

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.

How do I block seopass_run completely? +

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.

What MCP server provides seopass_run? +

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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →