summarize_report
Read the results.sarif an earlier draugr scan wrote and return its findings ranked by priority, deduplicated, with the rule documentation link for each.
Instructions
Read the results.sarif an earlier draugr scan wrote and return its findings ranked by priority, deduplicated, with the rule documentation link for each. Answers 'what should I fix first?' from a scan that already ran, without starting a new one. A severity gate such as --fail-on high judges each finding's rankedSeverity, not its severity, which is the scanner's rating. A finding the project accepted comes back in accepted, with why, until when and the file and line that record the decision; report it as a decision and do not propose fixing it. The git history of a descriptor rule's line records who wrote it, and report.json carries that history in descriptor.exclusions[].gitHistory. It covers the controls that scan ran and nothing else, so treat it as a floor to build on rather than a complete account of a codebase's security. Given a report.json, read the results.sarif in the same directory, since report.json holds the verdict and the fix list and names each finding only by its fingerprint.
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": {
"path": "<path>"
},
"name": "summarize_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | path to the results.sarif draugr scan wrote; report.json beside it holds the verdict and the fix list, and names each finding only by its fingerprint | |
| limit | No | maximum findings to return; defaults to 20 | |
| minPriority | No | only return findings at this priority or above: p1, p2, p3 or p4 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | Yes | the first thing to do: of the first actions at or above minPriority in fix_list's lists for this report, the one with the highest priority, the earlier list on a tie; the action's title is quoted | |
| note | No | ||
| feeds | No | exploitability datasets the scan consulted; absent means no finding was checked against KEV or EPSS | |
| total | Yes | findings the report judged, before any priority filter; excludes suppressed | |
| counts | Yes | every finding total counts, by rankedSeverity, before any priority filter | |
| accepted | No | the suppressed findings with why, until when and where each decision is written, most severe first, capped at limit; report each as a decision, never as work to fix | |
| findings | Yes | ||
| returned | Yes | ||
| suppressed | No | findings a recorded decision took out of the ranking; not part of total |