withdraw_resource_standby_request
Take back the standby request the creator has open on the connector. Takes no input.
A creator holds one standby request at a time, whichever resource it was for, so there is nothing to name: the picker the bot sent stops waiting for an answer. When none is open the call changes nothing and still succeeds. Only the account holder may do this. The REST twin is DELETE /v1/projects/{project}/resources/{resource}/standby/request.
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
Sending the same arguments twice changes nothing the second time.
Arguments
This tool takes no arguments.
What it returns
{ "data": { "status": "withdrawn" }, "meta": {}}How it fails
VALIDATION_FAILEDthe token is not the account holder's.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-recovery:delete.
How is this guide?
Last updated on