insertWhiteboardImage
Insert a real IMAGE (photo, screenshot, logo, picture) into a whiteboard — the storage-backed equivalent of insertImageInDocument. Provide the image as imageUrl (fetched and re-hosted), imageBase64, or imageBinary; for large files call createImageUploadSession(documentId) first then pass the retu...
This record as markdown: /tools/io-stablebaseline-sb/insertwhiteboardimage.md
What insertWhiteboardImage does on Stable Baseline
AI agents use insertWhiteboardImage 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 |
|---|---|---|---|
x | number | — | Top-left x on the canvas. Omit to auto-place. |
y | number | — | Top-left y on the canvas. Omit to auto-place. |
align | string | — | Horizontal alignment relative to existing content (placed below it). Ignored if x/y are provided. |
width | number | — | Display width in px (resize). Defaults to ~360. |
height | number | — | Display height in px. Derived from width at 4:3 if omitted. |
locked | boolean | — | Lock the placed image so it cannot be moved, resized, or deleted by hand (e.g. a deck-owned framed slide image that changes only via the deck conversation). Def |
caption | string | — | Optional caption shown as a text label grouped beneath the image. |
fileName | string | — | Optional original filename (for storage + type hinting). |
imageUrl | string | — | URL to fetch the image from, or an assetUrl returned by createImageUploadSession. |
documentId | string | Yes | The whiteboard's documentId. |
imageBase64 | string | — | Base64-encoded image bytes (a data: URL prefix is allowed). Best for small images. |
imageBinary | array | — | Raw image bytes as an array of 0-255 values (alternative to imageBase64). |
Parameters from the server's own tool schema.
Why insertWhiteboardImage is rated Medium
This tool creates new content (images and metadata) in a whiteboard document and persists it to cloud storage. While the action is reversible (images can typically be deleted), the primary function is to write/modify document state. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition The tool 'insertWhiteboardImage' creates and modifies whiteboard content by inserting images with options to add captions and resize.
Risk signalsAccepts file system path (fileName) · High parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs insertWhiteboardImage 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 insertWhiteboardImage, this is the rule to start with:
insertWhiteboardImage 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 insertWhiteboardImage call is checked against it from then on.
Questions about insertWhiteboardImage
Insert a real IMAGE (photo, screenshot, logo, picture) into a whiteboard — the storage-backed equivalent of insertImageInDocument. Provide the image as imageUrl (fetched and re-hosted), imageBase64, or imageBinary; for large files call createImageUploadSession(documentId) first then pass the returned assetUrl as imageUrl. The bytes are stored in the document-images bucket and the scene only holds a reference (never base64), exactly like pasted images. Options: caption (a text label placed + grouped beneath the image), width/height in px to RESIZE (if only one is given the other follows a 4:3 ratio; ~360px wide if neither), and placement via x/y (top-left) OR align ('left'|'center'|'right', positioned just below existing content) — omit both to auto-place to the right of the current content. After inserting, call getWhiteboardImage to verify. To move or resize the image later, patch its element via updateWhiteboardScene (mode:'patch' with {id, x, y, width, height}). For curated software-architecture ICONS (AWS/Docker/etc.) use addWhiteboardElements with an {type:'image', iconPath} spec instead. 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.
insertWhiteboardImage accepts 12 parameters: x, y, align, width, height, locked, caption, fileName, imageUrl, documentId, imageBase64, imageBinary. 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 insertWhiteboardImage: 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.
insertWhiteboardImage 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 insertWhiteboardImage 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 insertWhiteboardImage. 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.
insertWhiteboardImage 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