seopass_status
Fetch the stored in-session status and report for a SEOPass run.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/seopass-status.md
What seopass_status does on UnClick
AI agents call seopass_status to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes | The SEOPass run id returned by seopass_run |
Parameters from the server's own tool schema.
Why seopass_status is rated Low
This tool retrieves and reports pre-computed SEO analysis status from a prior run. It has no side effects, does not modify or delete data, does not execute operations, and does not involve financial transactions. It is a straightforward read operation typical of status/report endpoints. Severity is low because misuse would only expose SEO analysis results, not system-critical or high-impact data.
From the tool's definition Tool description uses 'Fetch' and 'report' language, indicating retrieval of stored status data with no modification.
Attacks that exploit this kind of access
The rule that runs seopass_status 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_status, this is the rule to start with:
seopass_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every seopass_status call is checked against it from then on.
Questions about seopass_status
Fetch the stored in-session status and report for a SEOPass run. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
seopass_status accepts 1 parameter: run_id. Required: run_id. 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_status: 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_status 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_status 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_status. 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_status 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue