chart.visualization.create
⚡ ACTION: Generate a chart image (PNG) from data — bar, line, pie, doughnut, radar, scatter. Returns a permanent image URL. Combine with data tools (climate.co2, census.population, finance.exchange_rates) to visualize any dataset. Powered by QuickChart (Chart.js).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/chart.visualization.create.md
What chart.visualization.create does on Apibase
AI agents call chart.visualization.create to retrieve information from Apibase 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 | Chart type: bar, line, pie, doughnut, radar, scatter, horizontalBar |
title | string | — | Chart title displayed at top |
width | integer | — | Image width in pixels (100-1000, default 500) |
height | integer | — | Image height in pixels (100-1000, default 300) |
labels | array | Yes | X-axis labels (e.g. ["Q1", "Q2", "Q3", "Q4"]) |
datasets | array | Yes | One or more datasets to plot |
Parameters from the server's own tool schema.
Why chart.visualization.create is rated Low
Even though chart.visualization.create 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 chart.visualization.create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chart.visualization.create, this is the rule to start with:
chart.visualization.create 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 Apibase, apply this rule, and every chart.visualization.create call is checked against it from then on.
Questions about chart.visualization.create
⚡ ACTION: Generate a chart image (PNG) from data — bar, line, pie, doughnut, radar, scatter. Returns a permanent image URL. Combine with data tools (climate.co2, census.population, finance.exchange_rates) to visualize any dataset. Powered by QuickChart (Chart.js). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
chart.visualization.create accepts 6 parameters: type, title, width, height, labels, datasets. Required: type, labels, datasets. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for chart.visualization.create: 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 Apibase. Nothing to install.
chart.visualization.create 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 chart.visualization.create 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 chart.visualization.create. 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.
chart.visualization.create is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue