uxpass_run

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 50 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/uxpass-run.md

WHAT IT DOES

What uxpass_run does on UnClick

AI agents invoke uxpass_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 run (takes precedence over pack_name)
`hats`	array	—	Reserved for future use. Currently ignored; the deterministic runner evaluates the full uxpass-core check set on every run.
`task_id`	string	—	Client-generated idempotency key (UUIDv5 from thread_id + prompt_hash + time_bucket recommended). Required for safe retry. If omitted, the server creates a fres
`pack_name`	string	—	Name of a registered UXPass pack; the pack's 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 uxpass_run is rated High

This tool triggers automated checks and operations against arbitrary URLs provided as arguments. While it does not delete data or move money, it executes external automated processes (deterministic check sets, screenshot capture, proof generation) whose behavior and side effects depend on user-supplied URL arguments.

From the tool's definition 'Run a UX journey/usability check synchronously against a URL. Executes the deterministic uxpass-core check set' — the tool executes external operations (UX checks, screenshots, mobile/desktop proofs) against a supplied URL whose effects are determined by the…

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

uxpass_run Rate-limited

uxpass_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": {
    "uxpass_run": {
      "limits": [
        {
          "counter": "uxpass_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 uxpass_run call is checked against it from then on.

FAQ

Questions about uxpass_run

What does the uxpass_run tool do? +

Run a UX journey/usability check synchronously against a URL. Executes the deterministic uxpass-core check set and returns the run id, status, UX Score, summary, and uxpass_receipt_v1. UIPass now owns visual/interface polish; this legacy UXPass runner still calls out when screenshots or mobile/desktop proof are missing for visible surfaces. Pass either url (a one-off check) or pack_name (resolves the registered pack's url). The hats parameter is accepted for forward compatibility but is currently ignored; LLM hats land in a later chunk. Response includes was_duplicate: boolean indicating whether the row was already present (idempotent retry). 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 uxpass_run accept? +

uxpass_run accepts 5 parameters: url, hats, task_id, 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 uxpass_run? +

Register the UnClick MCP server in PolicyLayer and add a rule for uxpass_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 uxpass_run? +

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

Can I rate-limit uxpass_run? +

Yes. Add a rate_limit block to the uxpass_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 uxpass_run completely? +

Set action: deny in the PolicyLayer policy for uxpass_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 uxpass_run? +

uxpass_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 →