Action confirmation & risk
How Syncanix decides what runs automatically and what needs a human yes.
Not every action should be treated the same way. Syncanix gates each one by how risky it is, so reading information is effortless while changing or deleting it always involves a deliberate decision.
Three tiers
- Read — runs automatically
- Actions that only look something up can run without interruption, so answering questions stays fast.
- Write — asks first
- Actions that change data pause for the user to confirm, with a clear summary of what will happen, before they run.
- Destructive — blocked by default
- Actions that delete or irreversibly change data are blocked unless you explicitly allow them, and can require step-up authentication and a typed confirmation.
Multi-step plans
When answering a request takes several actions, the assistant can present the whole plan first and run nothing until the user approves it — so there are no surprises mid-way.
You set the tier
Discovery proposes a side effect for each capability, and you confirm or override it in the dashboard. The tier you choose is what governs the action everywhere it can be invoked.
Confirmation in MCP clients
The same gating applies to MCP clients: write actions ask for an approve-or-decline, and destructive actions stay blocked. Actions that require step-up authentication are completed in the widget, where that prompt can be shown.