Environment tokens reach only records and actions, and can be revoked
An environment's own token (IB_ENVIRONMENT_TOKEN) on the environment's MCP server now gets the data tools only, as on the API: no longer the tools that write files, change schemas, grant roles or run tests. Revoke tokens on Settings → API keys ends every token of the environment, the full one and each role-bound one, and builds production again (or restarts development's dev server) so the app's code has the new one.
Transferring an app to another team now ends the sending team's environment tokens, deletes its deploy tokens and moves the app's Auditor reviews; production is built again and dev servers restart with the new tokens.
A deployment missing its secrets key now logs why every environment token is refused, instead of refusing them silently.
More in Environment tokens.