remove_resource_standby
Stop keeping a standby for one resource; the chat itself is untouched and the resource keeps its live chat.
The standby row is forgotten and mirroring into it stops. Automatic failover can no longer swap this resource until a new standby is linked. Only the project owner may do this; a resource with no standby succeeds with nothing to remove.
This tool is annotated destructive: a client that supports the annotation asks a human before running it. The REST twin is DELETE /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.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it.
Arguments
resource_id*stringUUID of the resource whose standby to remove.
What it returns
{ "data": { "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6", "standby": null }, "meta": {}}How it fails
VALIDATION_FAILEDthe token is not the project owner's.
RESOURCE_NOT_FOUNDresource_id is not a resource the token can see.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-recovery:delete.
How is this guide?
Last updated on