get_resource_standby
Read the standby kept for one resource — its health, whether posts are mirrored into it, and when it was last probed and written to.
A standby is a spare channel or group the bot already administers, linked to one resource so a ban can be answered by a swap. This reads it: health_status (with the connector's health_reason code when degraded), mirror_enabled, health_checked_at, last_mirrored_at, linked_at. The standby's own identifier on the platform is deliberately absent. The REST twin is GET /v1/projects/{project}/resources/{resource}/standby.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
resource_id*stringUUID of the resource whose standby to read.
What it returns
{ "data": { "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6", "mirror_enabled": true, "health_status": "healthy", "health_status_label": "Healthy", "health_reason": null, "health_checked_at": "2026-09-12T02:00:00Z", "last_mirrored_at": "2026-09-12T01:45:12Z", "linked_at": "2026-09-01T14:22:09Z" }, "meta": {}}How it fails
RESOURCE_NOT_FOUNDthe resource keeps no standby, or resource_id is not a resource the token can see.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-recovery:view.
How is this guide?
Last updated on
get_recovery_settings
Read one project's Disaster Recovery settings — automatic failover and its fee consent, how members are told after a swap, and whether a standby installation is kept.
list_recovery_incidents
List the Disaster Recovery incidents of the creator the token acts for — what the health probes found broken, open by default, with the reason in the connector's words.