AI agents call seopass_status 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 |
|---|---|---|---|
run_id | string | Yes | The SEOPass run id returned by a future seopass_run execution path |
Parameters from the server's own tool schema.
This tool retrieves status information about a SEOPass run. It performs no data modification, deletion, or external execution—just a query to obtain the current state of a resource. The note about 'persistence lands later' suggests the status-fetching mechanism is already functional while write capabilities are still in development, further confirming this is a read-only operation. Blast radius is minimal.
From the tool's definition Tool name 'seopass_status' and description 'Fetch the status for a SEOPass run' indicate a retrieval operation. The verb 'fetch' is characteristic of Read operations that query data without side effects.
Attacks that exploit this kind of access
Fetch the status for a SEOPass run. Chunk 1 reserves the tool shape; persistence lands later. 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.
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 →