Validate a fix
validate_fixRe-run a finding's attacks against the live target to confirm a fix worked. Returns a verdict: 'resolved' (no attack reproduces anymore), 'still_broken' (at least one still does, or the re-run could not confirm the fix), 'not_eligible' (mark the finding fixed first), or 'validating' (still running). A re-run often takes longer than this call waits, so expect 'validating': then re-read the finding with get_finding until its 'validating' field is false, rather than calling validate_fix again. A second call is refused while one runs, and every call uses one of the finding's 3 re-runs a day. Once 'validating' is false, status 'fixed_verified' means the fix is confirmed, 'regressed' means an attack still reproduces, and 'fixed' means the re-run could not confirm it. Requires the test:run scope.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"finding_id": "<finding_id>"
},
"name": "validate_fix"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| finding_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | The finding's lifecycle status after the validate. | |
| verdict | Yes | resolved: no attack reproduces anymore (finding fixed & verified). still_broken: at least one attack still reproduces, or the re-run could not confirm the fix, in which case the finding stays fixed and awaits the next re-test. not_eligible: mark the finding fixed before validating. validating: still running; re-read the finding with get_finding until its validating field is false. | |
| finding_id | Yes | ||
| replay_run_id | Yes | The replay run that re-ran the attacks; empty when none was spent. |