Where each tool is offered
The Access tab — choosing which channels carry each of your tools, how it sits alongside the channel and tool switches, and how fast a change takes effect.
Your tools are generated from your profile and answer on several channels at once: your MCP endpoint, your A2A endpoint, and in-page tools in a visitor’s browser. Settings → AI Agents → Access is where you decide which of those channels carries which tool.
Three things decide whether a given tool answers on a given channel, and they apply in that order.
1. What CoreLoop allows
Some combinations are decided in the product, not by you. A tool that sends something on your
behalf is never offered to an assistant running inside a visitor’s browser: send_inquiry is
available on MCP and A2A and nowhere else, because an in-browser agent has no way yet to ask the
visitor to confirm before it sends. Those cells are simply not shown in the table — a
switch that nothing could turn on is worse than no switch at all.
Other tools are allowed everywhere but start switched off on a channel. ask is
one: it answers on MCP and A2A out of the box, and its in-browser cell starts off.
CoreLoop’s own internal tools never appear here at all. They are never offered to outside assistants, so there is nothing to choose.
2. The Access table
Rows are your tools, columns are the three channels, and each cell is a switch. Only the account owner can change them; everyone else on the team sees the table read-only. Tools appear here as soon as they have been generated from your profile — you don’t have to publish first, so you can decide where each one answers before you go live.
Switching one cell off leaves the others on. Turning get_reviews off for in-browser agents
does not affect the same tool on MCP or A2A. That is the whole point of the table: one tool can
be public on one channel and withheld on another.
When a whole channel is switched off elsewhere, its column is tagged Off, so a column of “on” switches under it is not mistaken for something that is live.
3. The two switches that override everything
Two coarser switches sit above the table, and either one wins:
- Connections (the neighbouring tab in Settings → AI Agents) switches off a whole channel — every tool at once. Use it when you want to stop responses through a channel rather than tune what it carries.
- Tools (the Tools page in your dashboard) switches off a whole tool — on every channel at once. An inactive tool answers nowhere, whatever the Access table says.
Unpublishing your profile is the master switch above all of them, and it takes everything offline (see Where people and agents find you).
How fast a change takes effect
- MCP and A2A: immediately. The next request already sees the new state.
- In-browser tools: a short chain, not a single number. Changing a cell first queues a rebuild of the tool list your pages hand out. That runs in the background rather than while you wait — usually seconds — and until it finishes, pages are still handed the previous list. Once it has run, the list your pages publish is cached for 60 seconds, so a page loaded in the next minute can still see the previous state. And a page that is already open keeps the tools it has until its signed tool list expires, at most five minutes.
Nothing is lost in between, and switching back on restores the tool once that same chain has run through.