saveDatabaseForm
Make a form on a database table, or change one, in one call. Each answer adds a row to the table (read the answers with queryDatabaseRows) and each question fills one of its fields, named as getDatabase lists them; a field the table fills itself, such as Created time, cannot be asked. Leave form ...
This record as markdown: /tools/io-stablebaseline-sb/savedatabaseform.md
What saveDatabaseForm does on Stable Baseline
AI agents use saveDatabaseForm 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 |
|---|---|---|---|
form | string | — | An existing form's id or name. Leave out to make a new one. |
name | string | — | The form's name among the table's views. Needed for a new one; renames one. |
table | string | — | The table's id or name. Needed for a new form. |
title | string | null | — | The heading people see (default: the name). |
tellMe | boolean | — | Tell you about new answers. |
brandKit | string | null | — | A brand kit's id or name (listBrandKits) for the form's look; null: the usual look. |
sections | array | — | Instead of questions, for a form of several pages: each page's questions, as in questions. |
thankYou | object | null | — | What people see after sending. |
questions | array | — | The questions, in order, on one page. |
databaseId | string | Yes | The database's id, friendly id (DB-12) or exact name. |
description | string | null | — | Words under the heading. |
submitLabel | string | null | — | The send button's words (default: Send). |
Parameters from the server's own tool schema.
Why saveDatabaseForm is rated Medium
An AI agent can call saveDatabaseForm 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 (38 properties)
Attacks that exploit this kind of access
The rule that runs saveDatabaseForm 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 saveDatabaseForm, this is the rule to start with:
saveDatabaseForm 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 saveDatabaseForm call is checked against it from then on.
Questions about saveDatabaseForm
Make a form on a database table, or change one, in one call. Each answer adds a row to the table (read the answers with queryDatabaseRows) and each question fills one of its fields, named as getDatabase lists them; a field the table fills itself, such as Created time, cannot be asked. Leave form out to make a new one (give table and name): with no questions it starts with the table's first fields, as the app does. To change a form, name it in form and send only what changes: questions (or sections, for a form of several pages) replace its questions as a whole, and null clears a setting. whoCanAnswer: nobody (the default), people who can open the database, the organisation, or people outside it (chosen email domains or addresses, who prove their address with a code, or anyone with the link), where the organisation and its plan allow it; only someone who manages the table may open a form to people outside. The answer gives the link to share. Needs write access to the table. getDatabase with form reads one. 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.
saveDatabaseForm accepts 12 parameters: form, name, table, title, tellMe, brandKit, sections, thankYou, questions, databaseId, description, submitLabel. 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 saveDatabaseForm: 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.
saveDatabaseForm 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 saveDatabaseForm 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 saveDatabaseForm. 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.
saveDatabaseForm 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