Get application backups
get_application_backupsRead an Application's Backups section: whether it has a database, whether a deploy arms the database-backup default, and for each deployment its cluster, stack and backup posture (protection state, schedule, last restore point, why it is not protected). ready_vault_count with ready_vault_known says whether the organisation has a verified backup vault at all. Each deployment's keeping is what its backups keep, as the Backups page shows it. Read keeping.state first (known, no_policy or unknown); with unknown every fact is null, and null there never means none. keeps_days and keeps_everything are the policy; kept_count and oldest_kept_at are what is kept now; protected_since and last_restore_test are set only when their own _state is known. keeping is null until the deployment has a stack. A deployment's restore points are read with list_restore_points on its cluster and stack. Read-only; needs backups.read.
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": {
"application_id": "<application_id>"
},
"name": "get_application_backups"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| application_id | Yes | The Application's id. |