exportDatabaseRows
A table's rows as a file to download: CSV, or xlsx for Excel. Call getDatabase with table first for the field names where and select take. Made in the background from the rows matching where or view that the caller may see; returns an id. Call again with just id for its progress, then a link that...
This record as markdown: /tools/io-stablebaseline-sb/exportdatabaserows.md
What exportDatabaseRows does on Stable Baseline
AI agents use exportDatabaseRows to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | A download's id: its progress, then its link. |
sort | array | — | queryDatabaseRows' sort. |
view | string | — | A saved view: its filter, sort and fields. |
table | string | — | The table's id or name. |
where | object | — | Every row that matches: queryDatabaseRows' where. |
format | string | — | Default csv. |
select | array | — | Fields in order, by name. Default: every field, or the view's. |
timeZone | string | — | For dates, such as Australia/Sydney. Default UTC. |
databaseId | string | — | The database's id, friendly id (DB-12) or exact name. |
Parameters from the server's own tool schema.
Why exportDatabaseRows is rated Medium
An AI agent can call exportDatabaseRows faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs exportDatabaseRows 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 exportDatabaseRows, this is the rule to start with:
exportDatabaseRows stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 exportDatabaseRows call is checked against it from then on.
Questions about exportDatabaseRows
A table's rows as a file to download: CSV, or xlsx for Excel. Call getDatabase with table first for the field names where and select take. Made in the background from the rows matching where or view that the caller may see; returns an id. Call again with just id for its progress, then a link that works for 10 minutes. Excel cuts text longer than 32,767 characters in a cell; CSV keeps it whole. getDatabaseGuide topic finding_rows. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
exportDatabaseRows accepts 9 parameters: id, sort, view, table, where, format, select, timeZone, 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 exportDatabaseRows: 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.
exportDatabaseRows is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the exportDatabaseRows 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 exportDatabaseRows. 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.
exportDatabaseRows 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