Tools

Tools are actions the chatbot can take: find a product, check an order, book a meeting, save a lead, hand over to a person. Only the tools a message is about are sent to the model, so many tools don't slow it down.

Where tools come from

Kind	What it is
Built-in	Saving enquiries, handing over to a person and other chat basics.
Integrations	Tools of the integrations your company connected. You switch them on per chatbot.
Custom tools	Your own HTTP API, described once. See Your own tools and MCP.
MCP servers	Tools imported from an MCP server, following the same permissions and policies.

Each tool shows how many times it ran in the last 30 days, how often it succeeded and when it was last used.

When a tool runs

For every tool you choose, in this chatbot:

Setting	What happens
Runs automatically	The chatbot does it straight away (e.g. looks for free times).
Visitor confirms	The visitor clicks Confirm in the chat (e.g. a booking).
Team approves	It waits until someone on your team approves it.
Never	The tool is off.

By default: reading runs, writing asks the visitor, and money or deleting needs a person.

Waiting for approval

Actions held for your team appear on the Tools page (and in Approvals) with the conversation they came from. Approve runs the action, Reject stops it and the chatbot tells the visitor.

Chat Mode and Agent Mode

In Security you choose the chatbot's mode. Chat Mode answers, finds and recommends. Agent Mode may also create, update, book or cancel, as far as the tool firewall allows.

Connections and webhooks

Connections store credentials for your systems (API key, token, header, basic sign-in). They're encrypted, never shown again and never sent to the model. Several custom tools can share one connection.
Webhooks tell your system when something happens in the chat. Each delivery is signed with X-Oryvox-Signature. See Webhooks.