testpass_evidence
Fetch one TestPass item and its attached evidence by item_id or check_id. Use this when a chat agent needs proof for a specific checklist item.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/testpass-evidence.md
What testpass_evidence does on UnClick
AI agents call testpass_evidence 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 testpass_run |
item_id | string | — | Optional testpass_items row id |
check_id | string | — | Optional checklist id such as RPC-001 or MCP-007 |
Parameters from the server's own tool schema.
Why testpass_evidence is rated Low
This tool retrieves data (TestPass items and evidence) with no side effects. It is a straightforward read operation that queries a database or similar storage by identifier. The blast radius of misuse is minimal — an agent could retrieve unintended test evidence, but cannot modify, delete, or execute code.
From the tool's definition Tool name 'testpass_evidence' and description 'Fetch one TestPass item' — uses the verb 'Fetch' which indicates data retrieval. Parameters are 'item_id or check_id', both lookups. No modification, deletion, or execution is described.
Attacks that exploit this kind of access
The rule that runs testpass_evidence 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_evidence, this is the rule to start with:
testpass_evidence 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 testpass_evidence call is checked against it from then on.
Questions about testpass_evidence
Fetch one TestPass item and its attached evidence by item_id or check_id. Use this when a chat agent needs proof for a specific checklist item. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
testpass_evidence accepts 3 parameters: run_id, item_id, check_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 testpass_evidence: 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_evidence 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 testpass_evidence 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_evidence. 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_evidence 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