getDatabaseRow
Read one row in full: every field including long text, linked rows (with their ids), people (with their ids) and attachments, plus who created and last changed it, its version, and who it is shared with when you manage it. Call getDatabase with table first for the field names select and field tak...
This record as markdown: /tools/io-stablebaseline-sb/getdatabaserow.md
What getDatabaseRow does on Stable Baseline
AI agents call getDatabaseRow 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 |
|---|---|---|---|
field | string | — | Read one field's value in parts (for long text). |
rowId | string | Yes | The row's id (the first value of each row in queryDatabaseRows). |
table | string | Yes | The table's id or name. |
offset | integer | — | With field: the character to start from (nextOffset from the last answer). |
select | array | — | Optional: only these fields. Default: every field. |
history | boolean | — | Return the row's changes instead, newest first. |
databaseId | string | Yes | The database's id, friendly id (DB-12) or exact name. |
historyBefore | integer | — | With history: nextBefore from the last answer. |
Parameters from the server's own tool schema.
Why getDatabaseRow is rated Low
Even though getDatabaseRow 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs getDatabaseRow 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 getDatabaseRow, this is the rule to start with:
getDatabaseRow 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 getDatabaseRow call is checked against it from then on.
Questions about getDatabaseRow
Read one row in full: every field including long text, linked rows (with their ids), people (with their ids) and attachments, plus who created and last changed it, its version, and who it is shared with when you manage it. Call getDatabase with table first for the field names select and field take. Pass field, and offset for the next part, to read one very long value in parts. history lists the row's changes: who changed which values and when. getDatabaseGuide topic overview. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getDatabaseRow accepts 8 parameters: field, rowId, table, offset, select, history, databaseId, historyBefore. Required: rowId, table, 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 getDatabaseRow: 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.
getDatabaseRow 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 getDatabaseRow 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 getDatabaseRow. 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.
getDatabaseRow 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