Docs sectionsDatasource
Docs › Data and security

Datasource

Let agents read schemas and query real databases through an MCP server, while write access stays in your hands.

Declaring one

In Settings › Connections, each datasource has a type (for example PostgreSQL via MCP), an environment of PROD, STAGING or DEV, a host or tunnel, a user, and the name of the secret holding the password. Use a read-only user for PROD.

Tools agents can use

db.schemaReads table structure, DDL only.
db.queryRuns SELECT, checked by AST.
db.executeCommands that write data; always go through approval unless you've granted access for the whole session.

During a session

  • Click the Datasources pill in the composer and tick the datasources to use. The agent only sees what you ticked.
  • Switching database applies to this session only, on the same server and the same account.
  • Every query is classified by AST before it runs. A write to PROD stops and waits for you: Allow once or Deny.
  • You can grant INSERT for the whole session; the Revoke button puts later commands back to asking.
Never runs on its own, never skips on its ownApproval requests have no timeout. Until you answer, the agent simply waits; a command never runs by itself and is never rejected by itself.