The AI Settings window is a table where you decide, for each connection in the project, how far AI is allowed to go. The AI Assistant inside NeoSQL and MCP, which external AI tools call, both follow this table. AI and MCP explains how the two differ.
Where you can use itWebDesktopWithout signing inSigned inLocal projectsAccount projects
Open it with the AI Settings button at the top of the project screen. Local projects save it on this device; account projects save it on the NeoSQL server, and all project members follow it.
What's on the screen
| No. | Name | Description |
|---|---|---|
| 1 | Project and Public Connections area | The project policy and the policies of public connections. In account projects only the project owner can change them; other members see the Only the project owner can change AI settings for public Connections. notice. Local projects have no public/private split, so the area is named Connections and every connection is in it. |
| 2 | Allow persistent data-transfer approval for project non-owners option | When on, members other than the owner can also use the Auto-approve subsequent queries option on the data query approval card. Account projects only. |
| 3 | Enabled column | Whether AI may use this connection. When off, it cannot be picked as an AI Assistant context, and MCP rejects calls aimed at it. It cannot be turned on if no schema is selected in the connection settings. |
| 4 | Default column | Check it and pick a database and schema from the list next to it, and new chats start with that schema already picked as the context. MCP tools use this schema when a call does not name a target. You can set one for public connections and one for private connections; the public one comes first. |
| 5 | Schema changes column | When on, statements such as CREATE, ALTER and DROP written by the AI run without confirmation. When off, NeoSQL asks before running them. |
| 6 | Data changes column | When on, statements such as INSERT, UPDATE and DELETE written by the AI run without confirmation. For MCP it decides whether to auto-commit. |
| 7 | Allow data transfer column | When on, the AI reads real rows without an approval card when it needs them for an answer, and the result goes to the AI provider. When off, an approval card appears for every such query. |
| 8 | Always mask sensitive data column | When on, columns marked as sensitive are masked in results sent to AI and MCP regardless of the user's role. When off, masking follows the user's role. Not available in local projects. |
| 9 | Private Connections area | The policies of private connections you own. You can change them even if you are not the owner. Hidden when you have no private connections. |
| 10 | MCP Client Setup button | Opens the window for registering NeoSQL MCP in an external AI client. Desktop only. |
| 11 | Save button | Saves your changes. Dimmed until you change something, and hidden when there is nothing you can change. |
- Hover over a column header to see what the policy does.
- A connection labelled Design only has only a DBMS chosen, without database access details. It is used only by the ERD design tools of external MCP, never by the AI Assistant or for running queries, so its execution policy cells are unavailable.
- When the Enabled option is off, the other policy cells in that row cannot be changed.
Initial values
When you create a connection, its policy is created with these values.
| Policy | Initial value |
|---|---|
| Enabled | On |
| Default | Not set |
| Schema changes | Off |
| Data changes | Off |
| Allow data transfer | On |
| Always mask sensitive data | On in account projects. Not used in local projects |
| Allow persistent data-transfer approval for project non-owners | On (account projects) |
- So at first the AI reads real row values without asking and sends them to the AI provider. To confirm every time, turn off the Allow data transfer option.
Changing a connection's AI policy
- Click the AI Settings button at the top of the project screen.
- Turn cells on or off in the connection's row. To set the default context for new chats, check the Default cell (4) and pick a schema from the list next to it.
- Click the Save button (11). The window closes, and the change applies from the next request.
- If you try to close without saving, the Unsaved changes window appears.
- In account projects the public area and the private area are saved separately. If only one is saved, the Some settings were saved. Changes that could not be saved are still available. notice appears and the unsaved changes stay in the window.
- If your permissions or the connection list change while the window is open, saving fails and you are told to reload the project.
- Turning off the Enabled option of a connection that holds the Default setting also clears the default, without asking.
- There is one default per area. Checking the Default cell of another connection clears the earlier default in the same area.
Who can change it
| Project | Public connections and project policy | Private connections |
|---|---|---|
| Local project | The user of this device | Not distinguished (all in the public area) |
| Account project | The project owner only. The NeoSQL server also refuses to save from anyone else | The owner of that connection. Other people's private connections are not shown |
- If an account project has any public connection, the Default cell of private connections cannot be changed, because the public default comes first.
What the policy works with
The AI Settings table alone does not decide execution. The following come before it.
- If the connection's Protection mode field is Read-only (block non-SELECT), the AI does not run statements other than SELECT; if it is Confirm (DDL + risky DML), NeoSQL asks before running even when the Schema changes or Data changes option is on (Connection profiles).
- In account projects, users restricted by DDL Restriction cannot run schema changes through AI either.
- Sensitive data masking in account projects is based on the sensitive columns set on the Role Permissions tab (Column masking). The Always mask sensitive data option only decides whether that masking always applies to what is sent to AI and MCP, regardless of role.
Things to keep in mind
- The AI Settings table also applies to MCP. If you turn on the Schema changes option for the AI Assistant, DDL sent by an external AI through MCP also runs without confirmation.
- Do not turn on the Schema changes and Data changes options on production connections. SQL run by the AI is auto-committed and cannot be undone.
- With the Allow data transfer option on, real rows the AI reads (up to 10 at a time) go to the AI provider without asking. For databases with personal data, turn it off or turn off the Enabled option.
- Local projects have no masking. It is safer not to connect databases with sensitive values to AI in local projects.
Related screens
- AI Assistant: the panel that picks contexts and runs SQL cards according to this policy.
- AI and MCP: a table of how the AI Assistant and MCP each use this policy.
- MCP client setup: the window the MCP Client Setup button opens.
- Column masking: mark sensitive columns in account projects.
- Connection profiles: block or confirm AI execution with the connection's Protection mode field.