designDeckInWhiteboard
Create or refine a slide deck INSIDE an existing whiteboard by conversing with the AI design agent. Send a brief for a NEW deck, a change to an EXISTING one, or an answer to the agent's question. The agent builds a polished, on-brand deck and places it on the board; if the brief is ambiguous it a...
This record as markdown: /tools/io-stablebaseline-sb/designdeckinwhiteboard.md
What designDeckInWhiteboard does on Stable Baseline
AI agents use designDeckInWhiteboard 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 |
|---|---|---|---|
kind | string | — | Which engine. 'deck' (default) = the premium on-brand HTML deck (conversational, build + edit); 'illustration' and 'design' are conversational variants. 'expres |
title | string | — | Optional title. If omitted, a clear one is derived from the brief. |
deckId | string | — | Optional. An existing deck to continue designing (usually you pass sessionId instead; when both are given the session's deck wins). |
confirm | boolean | — | Set true ONLY after the user has approved the cost (50 for a build, 10 for an edit). Leave unset/false on the first call of a turn to receive the cost quote plu |
message | string | Yes | This turn's message in plain language: the design brief on the first turn, an edit instruction later, or the user's ANSWER to a clarifying question the agent as |
sessionId | string | — | The design conversation to continue, as returned by an earlier designDeckInWhiteboard call. Pass it together with message to answer a question, make an edit, or |
brandKitId | string | — | Optional brand kit id (from listBrandKits) to theme the deck. If omitted, the organisation's effective brand is used. |
documentId | string | Yes | The whiteboard the deck lives in. REQUIRED: a deck cannot exist without a whiteboard, and this is that whiteboard's id. If you do not already have a whiteboard |
slideCount | number | — | Optional target number of slides for a build turn (the composer adjusts to fit the story). Typical 6 to 12. |
attachments | array | — | Optional reference images for THIS turn (up to 8; images only). The agent lifts palette, layout, and tone from them (it does not pixel-copy). Non-image attachme |
Parameters from the server's own tool schema.
Why designDeckInWhiteboard is rated Medium
This tool creates or modifies a slide deck within a whiteboard — a reversible write operation. It generates and places structured content but does not execute code, delete data, or involve financial transactions. Misuse could result in unwanted content being added to a shared workspace, hence medium severity.
From the tool's definition 'Create or refine a slide deck INSIDE an existing whiteboard by conversing with the AI design agent' and 'the agent builds a polished, on-brand deck and places it on the board'
Risk signalsAccepts URL/endpoint input (attachments[].url) · High parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs designDeckInWhiteboard 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 designDeckInWhiteboard, this is the rule to start with:
designDeckInWhiteboard 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 designDeckInWhiteboard call is checked against it from then on.
Questions about designDeckInWhiteboard
Create or refine a slide deck INSIDE an existing whiteboard by conversing with the AI design agent. Send a brief for a NEW deck, a change to an EXISTING one, or an answer to the agent's question. The agent builds a polished, on-brand deck and places it on the board; if the brief is ambiguous it asks ONE clarifying question (answer with the same sessionId). Returns immediately; poll getDeckReplyInWhiteboard for the result. Use for building or editing slide decks / presentations. WHITEBOARD IS REQUIRED: a deck always lives inside a whiteboard, so documentId (the whiteboard's id) is required. If you do NOT already have a whiteboard id, ASK THE USER which whiteboard they want the deck designed in — do NOT create a whiteboard automatically. Only call createWhiteboard first if the user explicitly asks for a brand-new board; otherwise use the id of the whiteboard they name. FIRST vs FOLLOW-UP: the first call (from nothing) builds; a follow-up call (an answer, a change, or a new instruction) passes the sessionId (or the deckId) plus the new message. kind:'deck' (default) is the premium on-brand HTML deck; kind:'express' builds the native, deterministic branded-executive deck directly on the whiteboard (faster, lower fidelity, one-shot, not conversational). COST + APPROVAL: a build costs 50 credits and an edit 10; a clarifying question is FREE. Call FIRST without confirm to get the exact cost plus the workspace balance, show it to the user, and only call again with confirm:true once they agree. The fee is auto-refunded if a turn produces no change or fails. Returns sessionId (the conversation), deckId (the deck), status, turnType, started, awaitingUser, needsConfirmation, insufficientCredits, and assistantMessage. Export the finished deck with exportFromWhiteboard. 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.
designDeckInWhiteboard accepts 10 parameters: kind, title, deckId, confirm, message, sessionId, brandKitId, documentId, slideCount, attachments. Required: message, 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 designDeckInWhiteboard: 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.
designDeckInWhiteboard 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 designDeckInWhiteboard 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 designDeckInWhiteboard. 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.
designDeckInWhiteboard 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