updateDatabase

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/updatedatabase.md

WHAT IT DOES

What updateDatabase does on Stable Baseline

AI agents use updateDatabase 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 \| null	—
`name`	string	—
`moveTo`	object	—	Move the database. Give one of these. A project holds one database, so a project that has its database takes no other.
`tables`	array	—
`inherit`	boolean	—	true: access follows the database's project, workspace or organisation. false: only the people and teams it is shared with.
`databaseId`	string	Yes	The database's id, friendly id (DB-12) or exact name.
`description`	string \| null	—
`membersCanWrite`	boolean	—	Organisation databases: every member may add and change rows, not only read.

Parameters from the server's own tool schema.

RISK

Why updateDatabase is rated Medium

An AI agent can call updateDatabase 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[].addFields[].options.expression) · High parameter count (100 properties) · Bulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs updateDatabase 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 updateDatabase, this is the rule to start with:

updateDatabase Rate-limited

updateDatabase 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "updateDatabase": {
      "limits": [
        {
          "counter": "updatedatabase_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every updateDatabase call is checked against it from then on.

FAQ

Questions about updateDatabase

What does the updateDatabase tool do? +

Change a database: rename it, change its description or icon, switch inheriting access from its project, workspace or organisation on or off (inherit), let every member write to an organisation database (membersCanWrite), move it (moveTo a project, a workspace or the organisation), and in tables add a table (or copy one: copyOf) or, for an existing one, rename it, add, change or remove fields and views, set its row rule (who sees and edits which rows), its title field, row numbering and field order. Changes run in order; if one fails, the answer lists the ones already made. Removing a field removes every value in it; changing a field's type empties values that do not fit, unless convert gives each row's new value. Neither can be undone. The system fields (Created on, Created by, Updated on, Updated by) never change and stay last. Needs admin access to the database. To delete a table, use deleteDatabase. getDatabaseGuide topics structure and changing_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.

What parameters does updateDatabase accept? +

updateDatabase accepts 8 parameters: icon, name, moveTo, tables, inherit, databaseId, description, membersCanWrite. Required: databaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateDatabase? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateDatabase: 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.

What risk level is updateDatabase? +

updateDatabase is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit updateDatabase? +

Yes. Add a rate_limit block to the updateDatabase 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.

How do I block updateDatabase completely? +

Set action: deny in the PolicyLayer policy for updateDatabase. 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.

What MCP server provides updateDatabase? +

updateDatabase 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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →