testpass_run
Start a TestPass run against an MCP server. Seeds deterministic and agent checks from the given pack and returns the run id plus an initial verdict summary. Response includes was_duplicate: boolean indicating whether the row was already present (idempotent retry).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/testpass-run.md
What testpass_run does on UnClick
AI agents invoke testpass_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 |
|---|---|---|---|
pack_id | string | — | Pack slug (default: testpass-core) |
profile | string | — | Run profile (default: smoke) |
task_id | string | — | Client-generated idempotency key. The API requires UUID format; non-UUID values are deterministically converted to a stable UUIDv5-shaped id, so any string is s |
target_url | string | Yes | HTTP URL of the MCP server to test |
Parameters from the server's own tool schema.
Why testpass_run is rated High
This tool executes a testing framework against another MCP server. While testing itself is not inherently destructive, the ability to run arbitrary test packs against external systems represents an Execute capability—it triggers operations with side effects determined by the test parameters. The 'idempotent retry' note suggests state changes (run creation).
From the tool's definition The tool "Start a TestPass run" triggers an external operation (testing against an MCP server) whose effects depend on the arguments provided (the target server and test pack).
Attacks that exploit this kind of access
The rule that runs testpass_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 testpass_run, this is the rule to start with:
testpass_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every testpass_run call is checked against it from then on.
Questions about testpass_run
Start a TestPass run against an MCP server. Seeds deterministic and agent checks from the given pack and returns the run id plus an initial verdict summary. 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.
testpass_run accepts 4 parameters: pack_id, profile, task_id, target_url. Required: target_url. 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 testpass_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.
testpass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the testpass_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.
Set action: deny in the PolicyLayer policy for testpass_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.
testpass_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.
More on UnClick, and thousands of servers like it.
Across the catalogue