xCloud
delete_secret
Delete one stored secret by its name and scope: a value stored under the wrong name or at the wrong scope, or one no longer needed. The `application` and `environment` arguments name the scope as for `store_secret`. Destructive: needs a credential holding the destructive class (a signed-in session, or an account-wide token minted with `destructive`); the call creates a pending action, and the deletion runs only after a person approves it in the browser. Once it runs, the name leaves custody and no caller reads the value again. The vault holds the deleted value in its soft delete for its retention window, and no action reads or restores it. A store under the same name afterwards is a new value. A platform-minted name is refused `platform_minted_name`. A name still in use is refused `secret_in_use`: one a binding feeds, where the recorded manifest, a running copy, or an act in flight holds it, an upstream's key, or a realm route's or a push provider's credential. A use begun before the approval ends the pending action declined, and one begun after it ends the action failed with `secret_in_use`. A value already gone, or re-supplied, rotated, or stored again since the approval, completes with `deleted` false, and nothing is deleted.
Remote (network-hosted)
Other tools also called delete_secret?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"pattern": "^[a-zA-Z0-9][a-zA-Z0-9_-]{0,63}$",
"description": "The stored name to delete, as `list_secrets` lists it."
},
"request_id": {
"type": "string",
"description": "Your request identity for this pending action: any string you choose. Repeating the call with the same request_id, from the same account, while the earlier pending action is still live — requested, approved, or executing — answers that pending action again and creates no second one. Once it has completed, failed, been declined, or expired, the same request_id starts a new one. Omitted, every call creates a new pending action."
},
"application": {
"type": "string",
"description": "The application id whose scope holds the secret; omitted, the account scope."
},
"environment": {
"type": "string",
"pattern": "^(development|production)$",
"description": "Optional, and it rides `application`: the environment whose scope of that application holds the secret, `development` or `production`; absent, `production`. Each environment's value is deleted on its own call."
}
}
}