The restored database's row counts and the validation query result.
Workflows · Backup restores
A production restore waits on the database owner.
CC8.1 evidence for a restore: the backup, the target, the named approver and reason, and the validation result read back.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.
Agent request
Restore backup orders-2026-08-28-0200 into production/orders
A restore can replace newer production data or write a backup into the wrong database.
- Identity
- recovery-agent · Data platform
- Target
- production/orders
- Cost
- Recorded agent cost
- Evidence
- Backup identifier, creation time, restore plan, and validation query
SOC 2 CC8.1
Sensitive: waits for a named approver.
The backup identifier and time, the restore plan, the Database owner's reason, the validation result, and the CC8.1 test it supports.
Policy decision
Production restores require the Database owner.
Database owner
The action waits until this owner approves or denies it.
Tool call resumes
The backup tool restores the approved source to the recorded target and returns its result.
Tool call stays blocked
The restore does not start and production data remains unchanged.
Execution order
The agent request stops before the connected tool runs.
- 01Recovery agent requests the restore
- 02Deixic checks the backup, target, evidence, and policy
- 03Database owner decides
- 04Connected backup tool returns the restore result
- 05Deixic reads the result back and attaches the receipt to the test
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.