exportFromWhiteboard

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/exportfromwhiteboard.md

WHAT IT DOES

What exportFromWhiteboard does on Stable Baseline

AI agents use exportFromWhiteboard 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	—	What to export. 'deck' (default) = a finished deck that lives on the board (needs designId). 'canvas' = the whiteboard itself, its frames as slides, as PowerPoi
`format`	string	—	Output format. 'pptx' (default) = editable PowerPoint; 'pdf' = vector PDF; 'png' = one image per slide. kind 'canvas' exports 'pptx' only. HTML is not available
`designId`	string	—	The design to export (the deck id), as returned by designDeckInWhiteboard. Required for kind 'deck'; not used for kind 'canvas'.
`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, or (kind 'canvas') the whiteboard to export.

Parameters from the server's own tool schema.

RISK

Why exportFromWhiteboard is rated Medium

An AI agent can call exportFromWhiteboard faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

exportFromWhiteboard 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "exportFromWhiteboard": {
      "limits": [
        {
          "counter": "exportfromwhiteboard_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about exportFromWhiteboard

What does the exportFromWhiteboard tool do? +

Export from a whiteboard: a finished design (a deck) as an editable PowerPoint (PPTX), a PDF or PNG images, or the whiteboard canvas itself as a PowerPoint. LARGE EXPORTS FINISH IN THE BACKGROUND: if the export takes longer than one tool call can wait, this returns status:'exporting' with a jobId instead of the file. Wait about 30 seconds and call this tool AGAIN with the SAME arguments to collect it, and repeat until status is 'completed' and 'url' is present. Nothing is re-exported while a job is already running, so polling is cheap and safe. Download links are available for 1 hour. kind:'deck' (default) needs the whiteboard documentId and the designId (the deck), and renders the finished deck: 'pptx' = native, fully editable PowerPoint (real shapes and text, not screenshots); 'pdf' = vector, one page per slide; 'png' = one image per slide. kind:'canvas' needs only the whiteboard documentId and exports the board as PowerPoint ('pptx' only): every frame on the board becomes a slide, in the board's slide order, and a board with no frames becomes one slide. HTML is not an available format, so do not ask for it. Small deck exports come back as base64 in data (pptx/pdf); anything larger, and every png export, comes back as download links. Inside an organisation agent's job the export is kept with the job as a file instead, and the answer carries its fileId for the next tool to use. A design that is still generating, failed, or archived returns a clear message. 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.

What parameters does exportFromWhiteboard accept? +

exportFromWhiteboard accepts 5 parameters: kind, format, designId, brandKitId, documentId. Required: documentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on exportFromWhiteboard? +

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.

What risk level is exportFromWhiteboard? +

exportFromWhiteboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit exportFromWhiteboard? +

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.

How do I block exportFromWhiteboard completely? +

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.

What MCP server provides exportFromWhiteboard? +

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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →