saveDatabaseDashboard
Make a dashboard for a database, or change one, in one call that saves everything or nothing. Leave dashboard out to make a new one (give name). Each page lists its visuals: a candidate ref from getDatabase's profile, used as it is, or a spec (copy a candidate's spec and change it, or write one f...
This record as markdown: /tools/io-stablebaseline-sb/savedatabasedashboard.md
What saveDatabaseDashboard does on Stable Baseline
AI agents use saveDatabaseDashboard 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 |
|---|---|---|---|
name | string | — | The dashboard's name. Needed for a new one; renames an existing one. |
check | boolean | — | Check without saving. |
pages | array | — | |
filters | array | — | Filters for the whole dashboard. Replaces the ones it has. |
restore | integer | — | A version id from an earlier answer's undo: put the dashboard back as it was then. Pass only databaseId and dashboard with it. |
version | integer | — | The version you read, when changing a dashboard. |
personal | boolean | — | A new dashboard just for you, not shared with everyone who can open the database. |
dashboard | string | — | The dashboard's id or name. Leave out to make a new dashboard. |
background | object | — | canvas (behind the tiles) and wallpaper (around them): each { image: a picture id, fit: actual, fit or fill, transparency: 0 to 100 }, or null. |
databaseId | string | Yes | The database's id, friendly id (DB-12) or exact name. |
Parameters from the server's own tool schema.
Why saveDatabaseDashboard is rated Medium
An AI agent can call saveDatabaseDashboard 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 (44 properties)
Attacks that exploit this kind of access
The rule that runs saveDatabaseDashboard 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 saveDatabaseDashboard, this is the rule to start with:
saveDatabaseDashboard 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 saveDatabaseDashboard call is checked against it from then on.
Questions about saveDatabaseDashboard
Make a dashboard for a database, or change one, in one call that saves everything or nothing. Leave dashboard out to make a new one (give name). Each page lists its visuals: a candidate ref from getDatabase's profile, used as it is, or a spec (copy a candidate's spec and change it, or write one from getDashboardVisualGuide). To change a dashboard pass dashboard and the version you read. Name a page by its id or its name (with its id, name renames it); position moves it (1 is the first); filters replaces its own filters; background gives it its own (null: the dashboard's); detailFor makes it a detail page; remove takes it out. A visual with an id is changed (a new spec, or just a title) or taken out with remove; one without an id is added. Every spec is checked before anything is saved and each new visual's numbers are worked out once: one with nothing to show, or only one group, is left out and reported. New tiles go below the others unless the page's layout is tidy: the page is then laid out again in the order its visuals are listed (list them all, existing ones by id alone), so use it to improve or add to a page. size sets a tile's width. place puts a tile exactly where it says, the others flowing round it. A dashboard holds at most 20 pages (fewer on smaller plans) and 30 visuals (8 on Free), 24 on one page; one call takes 20 pages, so make a bigger change over several calls. check: true checks without saving. The answer says what was saved, what was left out, and how to undo it. After every save, look at each page you changed with getDashboardImage and keep changing it until the layout and the visuals look right. Needs write access to the database; a dashboard just for you (personal) needs only read access. 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.
saveDatabaseDashboard accepts 10 parameters: name, check, pages, filters, restore, version, personal, dashboard, background, databaseId. 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 saveDatabaseDashboard: 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.
saveDatabaseDashboard 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 saveDatabaseDashboard 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 saveDatabaseDashboard. 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.
saveDatabaseDashboard 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