Get the next remediation tasks
get_next_remediation_task_setGet open controls from the project's latest scan, with instructions.
customer_asserted=true means a member of your organisation edited the
task's title, category, or instructions. customer_edits lists the fields,
editor, and time.
Actionable work includes required controls and older nice_to_have controls,
which stay open until a scan closes them. A control covered by another is
withheld while its cover is pending. It returns if the customer reopens
it after the covering control completes.
Implement all fixes, commit them, then verify with trigger_analysis.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_next_remediation_task_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | Project ID (provide either project_id or project_name) | |
| project_name | No | Project name (provide either project_id or project_name) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | True when the call itself failed. False for successful calls, including a scan still running, an already approved plan, or a repository classified as non-agentic. The reason field describes these workflow states. | |
| reason | No | A stable snake_case code from the allowed set. Present on every error and on successful calls that carry a workflow state. | |
| message | No | Exactly one sentence written for the user. Never raw exception text or a backend error string, which may expose private details. | |
| scan_id | No | The scan of the approved plan's analysis job. Null when Trent does not name one: a legacy analysis, or a Trent version that does not send it. | |
| controls | No | Remaining actionable controls with implementation instructions, must_implement first, then by priority_rank, lowest first (priority_score, highest first, when no rank is served). customer_asserted=true means a member of your organisation edited this task's title, category or instructions; customer_edits lists which fields, who and when. A control on a ticket carries 'ticket' (key, url, trent_state): name the ticket when you work on the control. | |
| metadata | No | Caller metadata, such as 'expiration_warning'. Substantive results have their own fields. Never includes exception or backend error text, which may expose private details. | |
| next_steps | No | Recommended next actions, in order. | |
| controls_from | No | Which report the control_status values come from: scan_id, and report_is_stale / report_stale_reason when a newer scan exists than that report. | |
| latest_job_id | No | The newer scan's job ID when its plan cannot be read yet. | |
| latest_scan_id | No | The newer scan's id when its plan cannot be read yet. | |
| retry_after_seconds | No | With reason rate_limited, how many seconds Trent asks the caller to wait. | |
| analysis_in_progress | No | True when a scan other than this plan's is running or queued, so these tasks are from the last complete scan and change when it finishes; say so. | |
| classification_breakdown | No | Counts only the approved, not-yet-done controls this reply returns, by classification. Completed and excluded controls, covered controls withheld while their cover is pending, and controls outside the approval are not counted, so it is smaller than review_plan's classification_breakdown. |