getWhiteboard
Read a whiteboard: its metadata plus a summary of the canvas (element count, element types, and text labels on the board). Pass includeElements=true to also return the full Excalidraw scene ({elements, appState, files}) — needed if you intend to modify it and send it back via updateWhiteboardScen...
This record as markdown: /tools/io-stablebaseline-sb/getwhiteboard.md
What getWhiteboard does on Stable Baseline
AI agents call getWhiteboard 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 |
|---|---|---|---|
documentId | string | Yes | |
includeElements | boolean | — | When true, returns the full Excalidraw scene so it can be modified and written back. |
Parameters from the server's own tool schema.
Why getWhiteboard is rated Low
This tool retrieves and queries whiteboard data (metadata, canvas summary, visual elements). It has no parameters that trigger mutations, deletions, or external actions. The mention of 'includeElements=true' for potential later modification does not make this tool itself Write or Execute—it merely returns data in a format suitable for downstream modifications.
From the tool's definition Tool name is 'getWhiteboard' and description states 'Read a whiteboard: its metadata plus a summary of the canvas' and 'return the full Excalidraw scene'. The verbs are read, return, and view—all retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs getWhiteboard 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 getWhiteboard, this is the rule to start with:
getWhiteboard 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 getWhiteboard call is checked against it from then on.
Questions about getWhiteboard
Read a whiteboard: its metadata plus a summary of the canvas (element count, element types, and text labels on the board). Pass includeElements=true to also return the full Excalidraw scene ({elements, appState, files}) — needed if you intend to modify it and send it back via updateWhiteboardScene. FOR BEST RESULTS, also call getWhiteboardImage to render the board to an image and actually SEE it: the visual layout (positions, spacing, overlaps, colours, how shapes connect) is far easier to understand from the rendered picture than from the element list, so view it first to truly understand the board and to propose or verify edits accurately. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getWhiteboard accepts 2 parameters: documentId, includeElements. Required: documentId. 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 getWhiteboard: 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.
getWhiteboard 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 getWhiteboard 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 getWhiteboard. 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.
getWhiteboard 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