Token permissions (scopes)

What each of the 8 permissions allows, which tools it unlocks and which combinations we recommend.

Permissions (scopes) define what an AI assistant can do with an API token. You choose them once, when you create the token, in the “Token nou” (New token) card on the “Token-uri de acces (API)” (Access tokens (API)) page (blackbox.md/account/api-tokens, “Contul meu” (My account) → “Token-uri API” (API tokens)).

Available to: any customer signed in to blackbox.md. A token acts only on the account that created it.

The blackbox.md website is available in Romanian and Russian; this article quotes the Romanian labels with their English meaning.

How permissions work

There are 8 permissions. The first three are read-only and are checked by default. The other five are shown in red and are not checked by default.
The assistant sees only the tools the token allows. A tool that is not allowed is hidden; if the assistant calls it anyway, it gets the error missing_scope: this token does not have 'orders:write' (with the name of the missing permission).
Two tools need no permission: whoami (confirms the account and shows the permissions the token has and the ones it is missing) and list_vm_plans (the catalog of VPS plans, with prices).
A token's permissions cannot be changed after it is created. If you need one more permission, create a new token.
In the token list, the “Permisiuni” (Permissions) column shows the codes (for example servers:read), not the checkbox text.

The 8 permissions

Code	Checkbox on the page	Risk	Tools unlocked
`servers:read`	“Citește lista și statusul serverelor mele” (Read the list and status of my servers)	read-only, checked by default	`list_servers`, `get_server`, `get_server_resize_options`
`billing:read`	“Citește soldul, facturile și comenzile” (Read the balance, invoices and orders)	read-only, checked by default	`get_balance`, `list_transactions`, `list_orders`, `list_invoices`
`ssh_keys:read`	“Citește lista cheilor mele SSH” (Read the list of my SSH keys)	read-only, checked by default	`list_ssh_keys`
`servers:power`	“Controlează alimentarea serverelor (repornire/oprire/pornire)” (Control server power (reboot/stop/start))	red: interrupts the server's operation	`power_server`
`servers:credentials`	“Vizualizează parolele/accesul serverelor” (View server passwords/access)	red: root access to the servers	`reveal_server_credentials`, `reset_server_password`, `add_server_ssh_key`, `set_server_password_auth`, `list_server_ssh_keys`, `remove_server_ssh_key`, `get_server_ssh_access`
`orders:write`	“Plasează și modifică comenzi în numele meu” (Place and change orders on my behalf)	red: spends from your balance, can delete a server	`create_order`, `pay_order`, `cancel_order`, `resize_server`
`ssh_keys:write`	“Adaugă și șterge cheile mele SSH” (Add and delete my SSH keys)	red: changes the keys in your account	`add_ssh_key`, `delete_ssh_key`
`servers:exec`	“Rulează orice comandă ca root pe serverele mele” (Run any command as root on my servers)	red, the most dangerous: any command as root	`run_server_command`

To find out what each tool does, see List of MCP tools.

Important The checkbox text does not describe everything the permissions actually allow. “Vizualizează parolele/accesul serverelor” (servers:credentials) also allows resetting the root password, installing and removing SSH keys on the server, turning password login on or off, and issuing an SSH key for the assistant. “Plasează și modifică comenzi în numele meu” (orders:write) also allows upgrading a server (paid from your balance, with a server reboot) and canceling orders; canceling an order whose server is active deletes the server immediately, with all its data.

Warnings for the red permissions

Below each red permission you check, this text appears: “Atenție: cu această permisiune asistentul AI va putea ACȚIUNE. Acordați-o doar clienților în care aveți încredere — token-ul poate fi revocat oricând.” (Warning: with this permission, the AI assistant will be able to ACTION. Grant it only to clients you trust — the token can be revoked at any time.) In place of ACȚIUNE (ACTION), the warning shows:

Permission	Action in the warning
`servers:power`	“porni și opri serverele dvs.” (start and stop your servers)
`servers:credentials`	“vedea parolele și cheile de acces ale serverelor dvs.” (see the passwords and access keys of your servers)
`orders:write`	“cheltui bani și plasa comenzi în numele dvs.” (spend money and place orders on your behalf)
`ssh_keys:write`	“adăuga și șterge chei SSH din contul dvs.” (add and delete SSH keys in your account)
`servers:exec`	“rula orice comandă ca root pe serverele dvs.” (run any command as root on your servers)

How to choose permissions when you create a token

On blackbox.md, click “Cont client” (Customer account), then “Token-uri API” (API tokens) in the left menu (on a phone, open “Meniu cont” (Account menu) first).
In the “Token nou” (New token) card, fill in “Nume token” (Token name).
Under “Permisiuni” (Permissions), uncheck the read permissions the assistant does not need.
Check the red permissions only if the assistant needs to change something. Read the warning that appears below each one.
For full access, click “AI-administrator — acces complet” (AI administrator — full access): the button checks all 8 permissions and shows “Acces complet: asistentul va putea rula orice comandă ca root pe serverele dvs., vedea parole și chei și cheltui din sold. Exact ce are nevoie un administrator AI — nu trebuie să îi mai dați nimic în afară de token.” (Full access: the assistant will be able to run any command as root on your servers, see passwords and keys, and spend from your balance. Exactly what an AI administrator needs — you don't have to give it anything other than the token.) To drop a permission, uncheck it individually.
Click “Creează token” (Create token). How to copy and store the token is described in API tokens: creating, copying and revoking.

After the token is created, the form goes back to the three read permissions.

Recommended combinations

Profile	Permissions	The assistant can	The assistant cannot
Monitoring, read-only	`servers:read`, `billing:read`, `ssh_keys:read` (the default checkboxes)	see your servers and their state, upgrade options with prices, your balance, transactions, orders, invoices and the keys in your account	change anything, see passwords, spend money
Server operator, no access to money	the 3 read permissions + `servers:power` + `servers:credentials`; optionally `servers:exec`	reboot, stop and start servers, see and reset the root password, manage the keys on the server; with `servers:exec`, also run commands as root	place, pay for or cancel orders, upgrade servers
Full-access agent	all 8, with the “AI-administrator — acces complet” (AI administrator — full access) button	everything the MCP tools allow, including payments from your balance	top up your balance or pay by card

For a token with red permissions, keep action confirmation turned on in your AI client. The full recommendations are in Token and AI agent security. For example tasks with the permissions they need, see Example tasks for the AI assistant and the permissions they need.

Security Treat servers:credentials as root access, even without servers:exec. With it, the assistant sees the root password and can obtain an SSH access key (get_server_ssh_access), and an AI client that can run commands on your computer (for example Claude Code) can connect to the server over SSH on its own.

When the assistant is missing a permission

Ask the assistant to call whoami. The response shows the token's permissions and the list of the missing ones (missing_scopes).
On the “Token-uri de acces (API)” (Access tokens (API)) page, create a new token with the missing permission plus the ones you already use.
Replace the old token in your AI client: Connecting in the Claude app (custom connector) or Connecting from Claude Code, Cursor, VS Code and other clients.
Revoke the old token with “Revocă” (Revoke).

Frequently asked questions

Can I add a permission to an existing token? No. Create a new token with the permissions you want and revoke the old one.

The assistant recommends the “AI agent — full access” preset. Where do I find it? On the “Token-uri de acces (API)” (Access tokens (API)) page, the button is called “AI-administrator — acces complet” (AI administrator — full access). It checks all 8 permissions.

With orders:write, can the assistant pay by card or top up my balance? No. It can pay only from the balance you already have. Details in Orders, payments, cancellations and upgrades via AI.

With ssh_keys:write, does the assistant install keys on servers? No. This permission changes only the keys saved in your account. Installing or removing a key on a server requires servers:credentials.

Can I create a token with no permissions? Yes, if you uncheck all the permissions. The assistant will then have only whoami and list_vm_plans.