getDeckReplyInWhiteboard

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

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What getDeckReplyInWhiteboard does on Stable Baseline

AI agents call getDeckReplyInWhiteboard 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
`deckId`	string	Yes	The deck or illustration to poll, as returned by designDeckInWhiteboard or designIllustrationInWhiteboard.
`documentId`	string	Yes	The whiteboard that hosts the deck or illustration (it lives inside the board). REQUIRED.

Parameters from the server's own tool schema.

RISK

Why getDeckReplyInWhiteboard is rated Low

This is a polling/query tool that retrieves asynchronous operation results. It reads the current state of a design task and its output without modifying, executing, or deleting anything. The most severe action is a Read operation.

From the tool's definition The tool description indicates it retrieves the status and result of a prior design operation: 'Get the design agent's reply', 'returns the build status', 'Poll until ready', 'once ready, the slide'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getDeckReplyInWhiteboard 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 getDeckReplyInWhiteboard, this is the rule to start with:

getDeckReplyInWhiteboard Allowed

getDeckReplyInWhiteboard is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getDeckReplyInWhiteboard": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every getDeckReplyInWhiteboard call is checked against it from then on.

FAQ

Questions about getDeckReplyInWhiteboard

What does the getDeckReplyInWhiteboard tool do? +

Get the design agent's reply after calling designDeckInWhiteboard OR designIllustrationInWhiteboard: the status (thinking/building/ready) and EITHER the finished result (a deck's slide count + preview, or the placed illustration) OR a clarifying question to answer (call the SAME tool you started with, passing the sessionId + your answer). Poll until ready or a question appears. Give it the whiteboard documentId and the deckId (both returned by the tool you called). It returns the build status ('generating' while working, 'ready' when finished, 'failed' if it failed) plus, once ready, the slide count and a thumbnail image URL. IMPORTANT for the conversation: if the agent asked a CLARIFYING QUESTION instead of doing the work, this returns awaitingUser:true with pendingQuestion (and assistantMessage) — relay that question to the user, then call the SAME design tool again with the same sessionId and the user's answer as message to continue. It also returns the full conversation (history + status + pending question). A turn usually takes about 1 to 3 minutes, so poll every 15 to 30 seconds until it is 'ready' or awaitingUser is true. When ready, the deck or illustration has already been placed on the whiteboard; a deck can also be exported with exportFromWhiteboard. If a turn failed or produced no change, the user was not charged. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.

What parameters does getDeckReplyInWhiteboard accept? +

getDeckReplyInWhiteboard accepts 2 parameters: deckId, documentId. Required: deckId, documentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getDeckReplyInWhiteboard? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for getDeckReplyInWhiteboard: 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 getDeckReplyInWhiteboard? +

getDeckReplyInWhiteboard is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getDeckReplyInWhiteboard? +

Yes. Add a rate_limit block to the getDeckReplyInWhiteboard 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 getDeckReplyInWhiteboard completely? +

Set action: deny in the PolicyLayer policy for getDeckReplyInWhiteboard. 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 getDeckReplyInWhiteboard? +

getDeckReplyInWhiteboard 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 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →