Manage assistant access
See which assistants are connected and revoke them, switch MCP servers off, and choose which actions need an approval code.
The MCP Servers page in the dashboard is where you control AI assistants on your account. You can see which assistants are connected and cut one off, switch off servers you don't want assistants to use, and choose which actions wait for an approval code.
Open it from MCP Servers in the dashboard's top menu. The cards at the top show how many connections you have, how many servers are on, and your current approval policy. Click a card to jump to its tab.
See who's connected
The Connections tab lists every assistant that has access to your account, with the servers it can use, when you connected it, and when it last used each one.
An assistant gets separate access to each server. Claude connected to App Platform and DNS appears as one assistant with two servers.
- Revoke removes an assistant's access to one server. Its next request to that server fails, and it has to sign in again to get access back. Its other servers keep working.
- Disconnect all appears when an assistant has more than one server. It revokes them all at once and signs the assistant out of Kubana completely.
Both take effect immediately. Kubana asks you to confirm first.
Just connected an assistant and don't see it?
Some assistants only show up after their first request to a server. Ask it something, such as "list my apps", then come back to the page.
A connection marked Expired hasn't been used for about 30 days. The assistant has to sign in again before it can use that server. Assistants you use regularly renew their access on their own.
Switch a server off
The Servers tab lists the six Kubana MCP servers. Select one to see its details, then use the On / Off switch at the top right.
When a server is off:
- Every assistant's requests to it are refused. The assistant is told that you turned the server off in the dashboard, so it can tell you instead of showing a vague error.
- Assistants stay connected. Switch the server back on and they can use it again straight away, without signing in again.
Use Off to pause a server, and Revoke to remove an assistant's access for good.
Only want an assistant on one product?
Switch off the servers you don't use. For example, keep DNS on and switch off VPS, so no assistant can create or delete servers.
The server's page also lists every action it offers:
- Write actions change something. Each one shows Ask for code or Runs directly.
- Read actions only look things up and never ask for a code.
Choose when Kubana asks for a code
On the Approval policy tab, choose one policy for your whole account. It applies to every connected assistant.
| Policy | What it does |
|---|---|
| Recommended (default) | Asks for a code before actions that cost money, take something offline or touch secrets. Small configuration changes run straight away. |
| Custom | You choose which write actions ask for a code, server by server. |
| Never ask | No action asks for a code, including ones that cost money or delete data. |
Each policy shows how many write actions would ask for a code. Coverage by server shows the split for each server; click a server to see its actions.
Under Recommended, two actions only ask in some cases. Deploying an app asks for its first deploy, because that starts billing. Turning auto-deploy on asks, because it reveals the webhook secret. Under Custom, an action you select asks every time.
Pick actions one by one
- Choose Custom on the Approval policy tab, or click Choose per action on a server's page.
- On the Servers tab, open a server and switch each write action to Ask for code or Runs directly. Require all and Require none change all of that server's actions at once.
- Actions Kubana protects by default are tagged Recommended: code when you switch their code off, so you can spot them.
Kubana remembers your custom selection. If you switch to Recommended and later back to Custom, your choices are still there.
Save your changes
Nothing changes until you click Save changes in the bar at the bottom of the page. Discard reverts everything since your last save. If you try to leave the page with unsaved changes, Kubana checks with you first.
If your changes would stop any action from asking for a code, Kubana lists them before saving. Confirm with Save without codes.
Changes apply to the assistant's next request. Nothing needs restarting, and assistants don't need to sign in again.
Think twice before choosing Never ask
An assistant can misread a request, or follow instructions hidden in a web page or repository it reads. Without codes, it can create paid services, deploy, power off servers and delete data without checking with you. Prefer Custom, and keep codes on anything that costs money or deletes data.
Good habits
- Revoke assistants you no longer use, and switch off servers you don't need.
- Check the Connections tab now and then. An assistant you don't recognise is a reason to revoke it and change your password.
- If you get an approval email you didn't expect, don't share the code. Revoke that assistant on the Connections tab.
Last updated 19 October 2026 · Something missing or wrong? Tell us