Restrict which tools a Connector offers
Set the tool allowlist to control which MCP tools the organization can call.
The tool allowlist is the subset of a Connector's tools the organization may invoke. Changing it requires mcp.server.update, granted to tenant administrators or delegated through a custom role. It applies to Managed and Remote servers alike, and to every caller, whether an Agent in chat or an external MCP client.
Before you start
Reading the tools a server advertises opens a real MCP session with it, as you. On a server where each user links their own credential, that session uses yours, so link one first. See Link your credential to a Connector. On an unauthenticated server there is no credential to use and none to link: the session carries no Authorization header, and the listing you read is the one every caller gets.
A Managed Server must also be ready. A Remote Server must answer.
Set the allowlist
- Open the server from Connectors in the Portal sidebar.
- Select the Tool allowlist tab. The Portal asks the server which tools it offers.
- Leave Allow all tools on to permit every tool, including tools added later. Turn it off to select individual tools.
- In manual mode, select at least one tool.
- Select Save allowlist.
When the stored allowlist is empty, Allow all tools is on by default. Every discovered tool is checked and shown in a disabled, faded state. A nonempty stored allowlist opens in manual mode with its saved selections preserved.
From the allow-all state, turning off Allow all tools starts an empty manual draft. The Portal does not change permissions while you edit the draft. Select Save allowlist to apply it, or select Cancel to discard it and restore the saved state.

The listing includes every tool the server currently advertises. In manual mode, unselected tools remain visible so you can permit them next.
An allowlist entry that no tool matches is shown as Not offered. That is usually a typo, and a name nothing matches permits nothing.
An empty allowlist permits everything
The API still interprets tool_allowlist: [] as allow-all, not deny-all. It permits every tool the server offers, including tools added later. The Portal's Allow all tools switch represents this saved empty list.
The switch lets the Portal distinguish the saved allow-all state from a manual draft with no selections. Turning off the switch starts that empty draft, but the Portal prevents saving until at least one tool is selected. It does not change the saved permissions until Save allowlist. There is no Portal setting that saves a deny-all allowlist. To stop an organization calling a server at all, delete the server.
After you save a manual selection, only the selected tools can be called. Unselected tools and tools added later are not permitted.
What a blocked call looks like
The Gateway reads the allowlist from the database on every request, so tightening one takes effect at once and needs no redeploy.
A tool outside the list is removed from the server's tool listing before the listing reaches the client. A client that names the tool directly is refused before the request reaches the Connector, with Unknown tool: <name>.
That is the same answer a genuinely unknown tool gets. Withholding the name is intentional. A refusal that revealed the tool exists would tell a caller what an administrator chose to hide.
What members see
A member opening the Tool allowlist tab sees the saved tool names as read-only badges. They do not trigger a listing and cannot change the selection. When the allowlist is empty, the tab says every advertised tool is permitted.
The allowlist applies whatever the server's credential mode. An unauthenticated server is not an unrestricted one: a member reaches only the tools permitted by the server configuration, exactly as on a server where each user links their own credential.
When the listing fails
| Message | Cause | What to do |
|---|---|---|
| No credential is linked | You have no User Credential for this server, and it expects one | Link one, then try again |
| The Connector is not ready yet | The Managed workload has not started | Wait for Ready, then try again |
| The MCP Server could not be reached | The workload or remote endpoint did not answer, or did not complete an MCP handshake | Check the server, then try again |
A not-ready error offers only Try again. It does not suggest linking a credential, because the credential is not the problem.
Read the allowlist with the API
export BSQAI_TOKEN=sk-bsq-v1-...
export SERVER_ID="<server-id>"
curl "https://api.<platform-domain>/v1/mcp/servers/$SERVER_ID/available-tools" \
-H "Authorization: Bearer $BSQAI_TOKEN"{
"tools": [
{
"name": "resolve-library-id",
"description": "Resolves a package name to a library identifier.",
"in_allowlist": true
},
{
"name": "get-library-docs",
"description": "Fetches documentation for a library.",
"in_allowlist": false
}
],
"count": 2
}in_allowlist reports literal membership of the stored list. When the allowlist is empty every tool is permitted and in_allowlist is false for all of them, so read the flag alongside the server's tool_allowlist rather than instead of it.
Write the allowlist by sending tool_allowlist on the server update request. See MCP reference.
Related pages
Connect Microsoft 365 and Slack
Add the Outlook, Microsoft Teams, SharePoint, and Slack Connectors with your own app registration, so each member can use their own account in chat.
Link your credential to a Connector
Sign in to the upstream system with OAuth, or paste a token, so a Connector can act as you.