testpass_edit_item
Override the verdict and notes for a single check item in a TestPass run. Fail-to-pass edits are flagged in mc_signals.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/testpass-edit-item.md
What testpass_edit_item does on UnClick
AI agents use testpass_edit_item to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | Yes | Required reviewer note explaining the manual verdict edit |
run_id | string | Yes | The run the item belongs to |
item_id | string | Yes | The testpass_items row id (uuid) |
verdict | string | Yes | New verdict |
Parameters from the server's own tool schema.
Why testpass_edit_item is rated Medium
This tool modifies test run data (verdict overrides, notes updates) which affects QA/validation outcomes. While reversible (hence Write not Destructive), the ability to alter test verdicts could allow an AI agent to falsely mark failing checks as passing, circumventing quality assurance processes. High severity due to potential impact on software release quality and safety.
From the tool's definition Tool allows 'Override the verdict and notes for a single check item' — this modifies existing test data and verdicts reversibly. The description explicitly indicates it changes check results ('Fail-to-pass edits are flagged').
Attacks that exploit this kind of access
The rule that runs testpass_edit_item 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_edit_item, this is the rule to start with:
testpass_edit_item stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_edit_item call is checked against it from then on.
Questions about testpass_edit_item
Override the verdict and notes for a single check item in a TestPass run. Fail-to-pass edits are flagged in mc_signals. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
testpass_edit_item accepts 4 parameters: notes, run_id, item_id, verdict. Required: notes, run_id, item_id, verdict. 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_edit_item: 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_edit_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the testpass_edit_item 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_edit_item. 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_edit_item 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