Connect a client
Roll back a deployment
Redeploy an eligible earlier deployment. The project plan must support rollback, and the deployment must belong to this project.
Clients are told this tool can remove, overwrite or interrupt resources, or grant access. Set your client to ask before it runs it.
Queued work: send an idempotencyKey and reuse the same value when retrying this exact call.
Arguments
| Name | Type | Required | Limits |
|---|---|---|---|
deploymentId | string | Yes | At least 1 character(s) |
projectId | string | Yes | At least 1 character(s) |
idempotencyKey | string | Yes | At least 1 character(s) |
Full input schema
{
"type": "object",
"properties": {
"deploymentId": {
"type": "string",
"minLength": 1
},
"projectId": {
"type": "string",
"minLength": 1
},
"idempotencyKey": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"description": "Unique request key. Reuse this exact value when retrying the same operation."
}
},
"required": [
"projectId",
"deploymentId",
"idempotencyKey"
],
"additionalProperties": false
}Example call
The params of a tools/call request. Replace the placeholder values with your own IDs.
{
"name": "rollbackProject",
"arguments": {
"projectId": "REPLACE_WITH_PROJECT_ID",
"deploymentId": "REPLACE_WITH_DEPLOYMENT_ID",
"idempotencyKey": "REPLACE_WITH_IDEMPOTENCY_KEY"
}
} Result
The same data as the API operation, wrapped as {"untrusted_data": true, "source": "rollbackProject", "note": "...", "data": ...} so the model treats project content as data, not instructions.