getDashboardVisualGuide
How to write the spec of one kind of dashboard visual: its wells (what goes where, and how many), which must be filled, the summaries a value can use, its settings with their usual values, and a worked example to copy. Pass type from listDashboardVisualTypes. Use the spec in saveDatabaseDashboard...
This record as markdown: /tools/io-stablebaseline-sb/getdashboardvisualguide.md
What getDashboardVisualGuide does on Stable Baseline
AI agents call getDashboardVisualGuide 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 |
|---|---|---|---|
type | string | Yes | A visual type: card, kpi, gauge, bar, column, line, area, combo, pie, donut, treemap, funnel, waterfall, scatter, heatmap, table, matrix, slicer, text, image. |
settings | string | — | usual (the default): the settings most visuals need. all: the rarely used ones too. |
Parameters from the server's own tool schema.
Why getDashboardVisualGuide is rated Low
Even though getDashboardVisualGuide only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getDashboardVisualGuide 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 getDashboardVisualGuide, this is the rule to start with:
getDashboardVisualGuide 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 getDashboardVisualGuide call is checked against it from then on.
Questions about getDashboardVisualGuide
How to write the spec of one kind of dashboard visual: its wells (what goes where, and how many), which must be filled, the summaries a value can use, its settings with their usual values, and a worked example to copy. Pass type from listDashboardVisualTypes. Use the spec in saveDatabaseDashboard, then look at it with getDashboardImage. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getDashboardVisualGuide accepts 2 parameters: type, settings. Required: type. 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 getDashboardVisualGuide: 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.
getDashboardVisualGuide 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 getDashboardVisualGuide 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 getDashboardVisualGuide. 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.
getDashboardVisualGuide 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