getDatabase
Read a database's structure: its tables, each table's fields and saved views, the rule that decides who sees which rows, and your access. Call it with table before you query or write a table's rows: its fields are keyed by their exact names, each with its type and details (read only: never writte...
This record as markdown: /tools/io-stablebaseline-sb/getdatabase.md
What getDatabase does on Stable Baseline
AI agents call getDatabase 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 |
|---|---|---|---|
form | string | — | A form's id or name (table narrows it). |
table | string | — | One table's id or name: that table in full, with every choice and how each field is written. |
usage | boolean | — | Return its usage of each limit instead, with the part in the trash (with table: that table's too). |
cursor | string | — | With changes: nextCursor from the last answer. |
visual | string | — | With dashboard: a visual's id. |
changes | boolean | — | Return the database's changes instead, newest first (with table: that table's). |
profile | boolean | — | With table (a database's only table if left out): field facts and ready visuals. |
suggest | integer | — | With profile: visuals to offer (8). |
dashboard | string | — | A dashboard's id or name. |
databaseId | string | Yes | The database's id, friendly id (DB-12) or exact name. |
profileFields | array | — | With profile: only these fields. |
Parameters from the server's own tool schema.
Why getDatabase is rated Low
Even though getDatabase 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.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs getDatabase 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 getDatabase, this is the rule to start with:
getDatabase 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 getDatabase call is checked against it from then on.
Questions about getDatabase
Read a database's structure: its tables, each table's fields and saved views, the rule that decides who sees which rows, and your access. Call it with table before you query or write a table's rows: its fields are keyed by their exact names, each with its type and details (read only: never written), choices lists the options of its choice and status fields by name, and writing says how each kind of value is written (people, files, links). Use those names as they are in queryDatabaseRows (where, select, sort, groupBy, summaries), writeDatabaseRows and updateDatabase. databaseId takes the id, the friendly id (such as DB-12) or the exact name. changes lists who changed what and when: tables, fields, sharing, deleted and imported rows. usage tells how much of each limit it uses and how much of that is in the trash. getDatabaseGuide topic fields_and_types. Lists its dashboards too. table with profile: field facts and ready visuals for saveDatabaseDashboard. dashboard reads one; visual adds one visual's numbers. form reads one form: its questions, who may answer and its link. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getDatabase accepts 11 parameters: form, table, usage, cursor, visual, changes, profile, suggest, dashboard, databaseId, profileFields. Required: databaseId. 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 getDatabase: 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.
getDatabase 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 getDatabase 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 getDatabase. 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.
getDatabase 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