get_remediation
Fetch the saved LLM-generated remediation plan for a violation, with execution steps, impact, and confidence. Returns None if no suggestion is available.
Instructions
[READ] Fetch the persisted LLM-generated remediation Suggestion for one violation. Returns {summary, execution_plan.steps, impact_prediction (workload impact, maintenance window, rollback plan), confidence (0.0-1.0), human_review_required}, or None when no advisor suggestion has been generated for that violation yet (generate one via the vmware-harden CLI advisor). Read-only lookup in the local twin DB (~/.vmware-harden/twin.duckdb); no network calls and nothing is executed — suggestions are advisory only.
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": {
"violation_id": "<violation_id>"
},
"name": "get_remediation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| violation_id | Yes | The 'id' field of a row returned by list_violations (the violation's own id, not its rule_id or node_id). An id with no stored suggestion returns None rather than an error, so None means "not generated yet", not "not found". |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |