listWhiteboards
List AND grep the whiteboards in a project (hidden whiteboard-kind documents). query searches the title and friendlyId (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). This is the tool to find a board by name — listDocuments deliberately exclud...
This record as markdown: /tools/io-stablebaseline-sb/listwhiteboards.md
What listWhiteboards does on Stable Baseline
AI agents call listWhiteboards to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | With changedSince: boards per answer (default 30, at most 100). |
query | string | — | Grep across title and friendlyId. Substring by default; a regular expression when isRegex is true. |
offset | number | — | With changedSince: how many to skip (nextOffset from the last answer). |
isRegex | boolean | — | Treat `query` as a regular expression. |
timeZone | string | — | The IANA time zone the window and its times are in, such as Australia/Sydney. Default: the person's own (the zone their browser last saved), else UTC. |
projectId | string | — | |
workspaceId | string | — | With changedSince and no projectId: only what changed in this workspace. Neither: your whole organisation. |
changedSince | string | — | What changed: only what was added or edited from this point, newest change first, each with who changed it and when. A period: today, yesterday, this_week, last |
caseSensitive | boolean | — | Match case exactly. Default false. |
changedBefore | string | — | With changedSince given as a date: only what changed before this date (YYYY-MM-DD) or date and time. |
Parameters from the server's own tool schema.
Why listWhiteboards is rated Low
Even though listWhiteboards only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs listWhiteboards 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 listWhiteboards, this is the rule to start with:
listWhiteboards is read-only, so it stays allowed. 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 listWhiteboards call is checked against it from then on.
Questions about listWhiteboards
List AND grep the whiteboards in a project (hidden whiteboard-kind documents). query searches the title and friendlyId (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). This is the tool to find a board by name — listDocuments deliberately excludes whiteboards. Returns documentId, diagramId, title and timestamps for each. projectId is required unless changedSince is given. WHAT CHANGED: give changedSince (a period such as this_week, or a date) to list only the boards added or changed in that time, newest change first, each with change: what happened, when (in words, in the person's time zone), by whom (a person's name, and the agent's key when one did it). With no project named it covers a workspace (workspaceId) or your whole organisation. Only what the caller may open is listed. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listWhiteboards accepts 10 parameters: limit, query, offset, isRegex, timeZone, projectId, workspaceId, changedSince, caseSensitive, changedBefore. 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 listWhiteboards: 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.
listWhiteboards is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listWhiteboards 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 listWhiteboards. 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.
listWhiteboards 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