createDatabase
Create a database, with its tables and fields in one call. Say where it lives: projectId (one project), workspaceId (every project of a workspace) or organisationId (the whole organisation library). Each table takes a name, fields (each a name and a type, with options for its type) and optionally...
This record as markdown: /tools/io-stablebaseline-sb/createdatabase.md
What createDatabase does on Stable Baseline
AI agents use createDatabase 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 |
|---|---|---|---|
icon | string | — | An emoji or icon name. |
name | string | Yes | |
copyOf | string | — | A database to duplicate (id, DB-12 or name); asked again while it runs, its progress. |
tables | array | — | |
copyRows | boolean | — | Default true. |
projectId | string | — | Make it the project's database (a project holds one). |
description | string | — | |
workspaceId | string | — | Make it a workspace's database, shown in every project of the workspace. |
organisationId | string | — | Make it an organisation database (needs an organisation owner or admin). |
copyPersonalViews | boolean | — | Your own personal views and dashboards too. Default false. |
Parameters from the server's own tool schema.
Why createDatabase is rated Medium
An AI agent can call createDatabase 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 signalsAccepts freeform code/query input (tables[].fields[].options.expression) · High parameter count (38 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs createDatabase 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 createDatabase, this is the rule to start with:
createDatabase 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 createDatabase call is checked against it from then on.
Questions about createDatabase
Create a database, with its tables and fields in one call. Say where it lives: projectId (one project), workspaceId (every project of a workspace) or organisationId (the whole organisation library). Each table takes a name, fields (each a name and a type, with options for its type) and optionally a row rule. Types: text, long_text, url, email, phone, number, currency, percent, rating, auto_number, single_choice, multiple_choice, status, checkbox, date, datetime, duration, person, team, relation (rows of another table: name a table made in the same call, or give its id), lookup and rollup (values read through a relation), artefact_link (Stable Baseline documents, whiteboards, diagrams, plans, tasks or improvements), attachment, formula. A table with no fields starts with a text field called Name; every table also ends with Created on, Created by, Updated on and Updated by, kept by Stable Baseline. If any part fails, nothing is kept. The organisation's plan limits how many databases it can have, and a project holds one database: when the project already has its database, add tables to that one with updateDatabase instead. To duplicate one, give copyOf and a name: it is copied in the background, into the place given or the original's own. getDatabaseGuide topics structure and fields_and_types. 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.
createDatabase accepts 10 parameters: icon, name, copyOf, tables, copyRows, projectId, description, workspaceId, organisationId, copyPersonalViews. Required: name. 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 createDatabase: 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.
createDatabase 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 createDatabase 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 createDatabase. 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.
createDatabase 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