getWhiteboardGuide
Get the Stable Baseline whiteboarding guide (Markdown): when to use stencils vs architecture icons vs code/BPMN diagrams vs plain shapes vs real images vs frames/presentations, how to lay out and verify a board, and how to edit a large board safely (patch by id, never replace). Call before author...
This record as markdown: /tools/io-stablebaseline-sb/getwhiteboardguide.md
What getWhiteboardGuide does on Stable Baseline
AI agents call getWhiteboardGuide 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.
Why getWhiteboardGuide is rated Low
This tool retrieves and returns instructional documentation about whiteboarding best practices. It performs a read-only query operation that returns static or reference material to inform the user's actions, but does not itself create, modify, delete, or execute any operations. No data is changed, no external systems are triggered, and no irreversible actions occur as a result of calling this tool.
From the tool's definition Tool name 'getWhiteboardGuide' and description 'Get the Stable Baseline whiteboarding guide' indicates retrieval of documentation/guidance material with no side effects.
Attacks that exploit this kind of access
The rule that runs getWhiteboardGuide 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 getWhiteboardGuide, this is the rule to start with:
getWhiteboardGuide 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 getWhiteboardGuide call is checked against it from then on.
Questions about getWhiteboardGuide
Get the Stable Baseline whiteboarding guide (Markdown): when to use stencils vs architecture icons vs code/BPMN diagrams vs plain shapes vs real images vs frames/presentations, how to lay out and verify a board, and how to edit a large board safely (patch by id, never replace). Call before authoring a non-trivial whiteboard. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getWhiteboardGuide: 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.
getWhiteboardGuide 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 getWhiteboardGuide 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 getWhiteboardGuide. 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.
getWhiteboardGuide 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