Rollback Simulated 3 MCP tools
Rollback Engine
Rollback flow with version tracking visualization.
How you use it
On failed health/promote: rollback_plan → execute → rollback_enforce. Do not improvise git reverts outside the engine when policy owns rollback.
Token savings
Structured rollbacks beat chaotic “which commit was good?” archaeology under pressure.
Consistency
Rollback targets and evidence are version-tracked the same way every time.
In action
Rollback
Trigger
Health red after promote.
Plan
Track
Enforce
Interactive demo
Rollback flow Idle
- Current: v2.4.1-rc1 (failing)
- Target: v2.3.2
- Deploying previous artifact…
- ✓ Traffic shifted · error rate 0.01%
Simulated behavior only — does not execute proprietary AGS engine code.
Diagram
Example usage
# MCP: rollback_plan
{ "env": "prod" }
# MCP: rollback_enforce
{ "env": "prod", "toVersion": "1.4.2" } Docs →- rollback_get
- rollback_plan
- rollback_enforce