Skip to main content
Glama

Retest a Guarita finding

retest_finding
Idempotent

Re-checks a previous finding on the published app. A finding that a single basic module can re-check on its own is re-tested in place: only that check runs again, without AI, and it does not consume the monthly round quota (a per-account daily limit applies instead). Any other finding (AI analysis, attack-chain, authenticated or compliance checks) queues a full round, as before. Poll the returned scan_id with get_scan_summary; the response carries retest_mode and, for in-place re-checks, verification_id and the initial verdict.

Input Schema

NameRequiredDescriptionDefault
scan_idYes
finding_idYes
idempotency_keyYesStable per user intent; reuse the same value when retrying this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources