exportFromWhiteboard
Export a design that lives in a whiteboard to an editable PowerPoint (PPTX), PDF, PNG images, or raw HTML. Give it the whiteboard documentId and the designId (the deck). kind:'deck' (default) renders the finished deck via the export worker: 'pptx' = native, fully-editable PowerPoint (real shapes ...
This record as markdown: /tools/io-stablebaseline-sb/exportfromwhiteboard.md
What exportFromWhiteboard does on Stable Baseline
AI agents call exportFromWhiteboard 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 |
|---|---|---|---|
kind | string | — | Which engine. 'deck' (default). |
format | string | — | Output format. 'pptx' (default) = editable PowerPoint; 'pdf' = vector PDF; 'png' = one base64 image per slide; 'html' = the design's self-contained HTML. |
designId | string | Yes | The design to export (the deck id), as returned by designDeckInWhiteboard. |
brandKitId | string | — | Optional brand kit id (reserved for future per-export theming; the design is already branded, so this is usually unnecessary). |
documentId | string | Yes | The whiteboard that hosts the design. |
Parameters from the server's own tool schema.
Why exportFromWhiteboard is rated Low
This tool reads/exports existing whiteboard content into various formats. It does not create, modify, or delete any data — it only retrieves and converts existing designs into output formats. The operation is non-destructive and read-only in nature.
From the tool's definition Export a design that lives in a whiteboard to an editable PowerPoint (PPTX), PDF, PNG images, or raw HTML... Returns the file as base64 in data
Attacks that exploit this kind of access
The rule that runs exportFromWhiteboard 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 exportFromWhiteboard, this is the rule to start with:
exportFromWhiteboard 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 exportFromWhiteboard call is checked against it from then on.
Questions about exportFromWhiteboard
Export a design that lives in a whiteboard to an editable PowerPoint (PPTX), PDF, PNG images, or raw HTML. Give it the whiteboard documentId and the designId (the deck). kind:'deck' (default) renders the finished deck via the export worker: 'pptx' = native, fully-editable PowerPoint (real shapes and text, not screenshots); 'pdf' = vector, one page per slide; 'png' = one image per slide (returned as a base64 array); 'html' = the self-contained deck HTML. Returns the file as base64 in data (pptx/pdf/html) or per-slide base64 in slides (png). The design must be finished; one that is still generating, failed, or archived returns a clear message. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
exportFromWhiteboard accepts 5 parameters: kind, format, designId, brandKitId, documentId. Required: designId, 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 exportFromWhiteboard: 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.
exportFromWhiteboard 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 exportFromWhiteboard 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 exportFromWhiteboard. 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.
exportFromWhiteboard 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