Tool interruptions
Overview
By default a user can interrupt the agent at any point, including while a tool is executing. For some tools this is undesirable: a payment confirmation or a compliance disclaimer read out after a lookup should be delivered in full.
The interruption_mode field controls this per tool. It is available on webhook tools, client
tools, system tools, and MCP servers.
Interruption modes
When several tools run in parallel, the strictest mode among them applies for that turn.
The boolean disable_interruptions field is deprecated. Use interruption_mode instead. The two
fields are kept in sync, so disable_interruptions: true is equivalent to interruption_mode: "disable_during_tool_and_turn" and existing integrations continue to work unchanged.
Configuration
Update via the dashboard
Update via the CLI
Update via the API
MCP servers
An MCP server carries its own interruption_mode,
which applies to every tool it exposes. Individual tools can override it through the server’s
tool_config_overrides, where the value set on a tool takes precedence over the server default.
Best practices
- Use
disable_during_toolwhen the tool call itself must complete, such as a transfer or a keypad sequence, but the user should be able to interrupt the response afterwards. - Use
disable_during_tool_and_turnwhen the response that follows the tool must be heard in full, such as a disclaimer or a confirmation read-back. - Leave the default
allowin place elsewhere, since suppressing interruptions makes the conversation feel less responsive.