Get backup posture
get_backup_postureAnswer whether data is protected, and if not why not (the twin of the Backups posture the portal renders). scope=organisation is the fleet rollup with the vault counts, scope=cluster adds every stack on one cluster, scope=stack is one stack's protection state, schedule, vault, data asset counts, last restore point and failing runs in the last 24 hours. protection_state is protected, unprotected or unknown - unknown means Ankra could not establish it, NOT that the stack is unprotected. protected says a policy is declared, NOT that copies are being taken: a refused scheduled backup writes no run, so failing_runs_24h stays 0 and next_scheduled_at keeps moving. not_capturing with its reason and action, stale with its reason, and last_complete_restore_point_at null are what say no restore point is being taken or none ever completed; report those, never call such a stack backed up. Read-only. Only offered when backups are enabled for the organisation.
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_backup_posture"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Which question to answer. Omit to derive it: a stack_name means the stack, a named or selected cluster means that cluster, neither means the whole organisation. Pass organisation explicitly to get the fleet answer from inside a cluster-bound conversation. | |
| cluster_id | No | UUID of the cluster. Alternative to cluster_name. | |
| stack_name | No | Stack to report on, for scope=stack. | |
| cluster_name | No | Exact name of the cluster. Optional when a cluster is already selected in the conversation. |