uxpass_status
Fetch the status, UX Score, summary, and uxpass_receipt_v1 for a UXPass run.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/uxpass-status.md
What uxpass_status does on UnClick
AI agents call uxpass_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 run id returned by uxpass_run |
Parameters from the server's own tool schema.
Why uxpass_status is rated Low
This tool retrieves status and metrics information from a UXPass run. The verb 'Fetch' and the data types being retrieved (status, score, summary, receipt) indicate a pure read operation with no capability to modify, execute code, or cause destructive actions. The low blast radius of misuse reflects that an AI agent retrieving UXPass metrics poses minimal risk.
From the tool's definition Tool description explicitly states 'Fetch the status, UX Score, summary, and uxpass_receipt_v1' — all read operations that retrieve data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs uxpass_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 uxpass_status, this is the rule to start with:
uxpass_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 uxpass_status call is checked against it from then on.
Questions about uxpass_status
Fetch the status, UX Score, summary, and uxpass_receipt_v1 for a UXPass run. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
uxpass_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 uxpass_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.
uxpass_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 uxpass_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 uxpass_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.
uxpass_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