listDatabases
List the databases you can use, with their tables and row counts. A database holds tables of rows, like a workbook holds sheets, and lives in a project, a workspace or the whole organisation. Pass projectId to see what a project can use (its own databases plus its workspace's and the organisation...
This record as markdown: /tools/io-stablebaseline-sb/listdatabases.md
What listDatabases does on Stable Baseline
AI agents call listDatabases to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | Find databases by name or friendly id, and tables by name. Ignores case. |
cursor | string | — | With changes: nextCursor from the last answer. |
changes | boolean | — | Owners and admins: every change in the organisation's databases instead. |
trashed | boolean | — | List the databases in the trash that you manage instead. |
projectId | string | — | List what this project can use: its databases, its workspace's and the organisation's. |
workspaceId | string | — | List the workspace's databases and the organisation's. |
includeTables | boolean | — | Include each database's table names and row counts (default true). |
organisationId | string | — | List every database in the organisation that you can read. Optional when your connection belongs to one organisation. |
Parameters from the server's own tool schema.
Why listDatabases is rated Low
Even though listDatabases only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs listDatabases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listDatabases, this is the rule to start with:
listDatabases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every listDatabases call is checked against it from then on.
Questions about listDatabases
List the databases you can use, with their tables and row counts. A database holds tables of rows, like a workbook holds sheets, and lives in a project, a workspace or the whole organisation. Pass projectId to see what a project can use (its own databases plus its workspace's and the organisation's), workspaceId for a workspace (its own plus the organisation's), or organisationId (or nothing) for every database in the organisation that you can read, wherever it lives. query finds databases by name or friendly id (such as DB-12) and tables by name. trashed lists databases in the trash that you manage. Organisation owners and admins: changes lists who changed what in every database, newest first. Next: getDatabase for a database's fields, then queryDatabaseRows to ask questions of a table. getDatabaseGuide explains every database tool by topic (overview first). It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listDatabases accepts 8 parameters: query, cursor, changes, trashed, projectId, workspaceId, includeTables, organisationId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for listDatabases: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Stable Baseline. Nothing to install.
listDatabases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listDatabases rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for listDatabases. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
listDatabases is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue