generate_echarts
Generate visual charts using Apache ECharts with an arbitrary ECharts option. This offline server renders PNG through ECharts SVG SSR and rsvg-convert.
This record as markdown: /tools/54dabang-kylin-arm64-64kb-page-size-mcp/generate-echarts.md
What generate_echarts does on Kylin Offline MCP ECharts
AI agents invoke generate_echarts to trigger actions in Kylin Offline MCP ECharts. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why generate_echarts is rated High
The tool executes a rendering pipeline (ECharts SVG SSR → rsvg-convert) with arbitrary user-supplied ECharts options, triggering external processes on the server. While its primary output is a PNG chart, it runs server-side code/processes with arbitrary input, placing it in the Execute category.
From the tool's definition 'Generate visual charts using Apache ECharts with an arbitrary ECharts option' and 'renders PNG through ECharts SVG SSR and rsvg-convert'
Attacks that exploit this kind of access
The rule that runs generate_echarts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kylin Offline MCP ECharts, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_echarts, this is the rule to start with:
generate_echarts stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kylin Offline MCP ECharts, apply this rule, and every generate_echarts call is checked against it from then on.
Questions about generate_echarts
Generate visual charts using Apache ECharts with an arbitrary ECharts option. This offline server renders PNG through ECharts SVG SSR and rsvg-convert. It is categorised as a Execute tool in the Kylin Offline MCP ECharts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kylin Offline MCP ECharts MCP server in PolicyLayer and add a rule for generate_echarts: 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 Kylin Offline MCP ECharts. Nothing to install.
generate_echarts is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_echarts 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 generate_echarts. 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.
generate_echarts is provided by the Kylin Offline MCP ECharts MCP server (54dabang/kylin-arm64-64kb-page-size-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kylin Offline MCP ECharts, and thousands of servers like it.
Across the catalogue