Your connection·private data

Query Connection (read-only)

Run one read-only SQL statement against a Postgres or BigQuery connection the caller owns and return the rows as research data. Writes and DDL are rejected; Postgres runs inside a read-only transaction scoped to the connection's allowed schemas, and BigQuery enforces a per-query scan-byte ceiling. Results are row-capped and flag truncation.

Requires your own connectionYour Postgres or BigQuery connection

Access

This tool reads a data source you connect. Cortexa hosts no dataset behind it and nothing here is publicly queryable — there is no result to show a visitor, only the shape of the call. Add a connection in Settings → Connections, and the agent can use it in your own sessions.

Works with: Postgres, BigQuery
Scope: A single SELECT/WITH statement inside the connection's allowed schemas or datasets.

Access is read-only and re-authorized on every call against the connection's owner, your active workspace, and any explicit grants. Credentials stay encrypted at rest and are never returned by a tool.

Schema

JSON Schema the agent (or your API call) must match.

View JSON schemaExpand

JSON · 21 lines · 450 chars

Examples (1)

Illustrative only — the ids below are placeholders. Real ids come from list_connections at run time and are scoped to the caller.

Count rows in an allowed table

input

JSON · 5 lines · 109 chars

Expected response keys: columns, rows, rowCount

Identifiers

Catalog ID: query_connection
Agent tool: query_connection
Added: 2026-07-26 09:40Z
Tags: connection, private, read-only, sql, query

Query Connection (read-only)

Requires your own connectionYour Postgres or BigQuery connection

Access

Works with: Postgres, BigQuery
Scope: A single SELECT/WITH statement inside the connection's allowed schemas or datasets.