Connecting an app, an MCP server or an HTTP group doesn't automatically grant any digital human access to it — you decide who can use what, and under what conditions, from each connection's management page.
Granting access to a digital human
In the Connected digital humans section, each digital human has a toggle: turn it on to grant access to all of that connection's tools at once, turn it off to revoke it. You can search by name and page through the list if you have many digital humans.
Choosing when each tool can be used
In Tool permissions, each tool (grouped into read-only and write) has one of these policies — set individually or in bulk per section:
| Policy | What it does |
|---|---|
| Allow always | The digital human uses it without asking you anything. |
| Require approval | Before running it, the digital human shows you a card to approve or decline the action. |
| Block | The digital human can't use it, even if it has access to the connection. |
By default, read-only tools are set to allow and write tools require approval — a sensible starting point you can adjust at any time.
When a tool is missing mid-chat
If a digital human needs a tool it doesn't have while you're chatting, Brain surfaces it right there: it offers to connect it (if no one has connected it yet) or grant access (if it's already connected but not assigned to that digital human) — without leaving the conversation.