generate_heatmap_chart
Generate a heatmap chart to display intensity distribution.
This record as markdown: /tools/54dabang-kylin-arm64-64kb-page-size-mcp/generate-heatmap-chart.md
What generate_heatmap_chart does on Kylin Offline MCP ECharts
AI agents use generate_heatmap_chart to create or update resources in Kylin Offline MCP ECharts, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kylin Offline MCP ECharts environment.
Why generate_heatmap_chart is rated Medium
This tool generates visualization output (a heatmap chart in SVG format) based on input parameters. It is a Write operation because it creates/produces data (the chart artifact), but with no destructive, financial, or arbitrary execution capability. The severity is low because the output is a static visualization with no side effects on underlying data, system state, or financial consequences.
From the tool's definition Tool name 'generate_heatmap_chart' and description 'Generate a heatmap chart to display intensity distribution' indicate chart/image generation. The server description confirms this is an 'offline charts' generator using 'Apache ECharts SVG SSR'.
Attacks that exploit this kind of access
The rule that runs generate_heatmap_chart 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_heatmap_chart, this is the rule to start with:
generate_heatmap_chart stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_heatmap_chart call is checked against it from then on.
Questions about generate_heatmap_chart
Generate a heatmap chart to display intensity distribution. It is categorised as a Write tool in the Kylin Offline MCP ECharts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kylin Offline MCP ECharts MCP server in PolicyLayer and add a rule for generate_heatmap_chart: 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_heatmap_chart is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_heatmap_chart 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_heatmap_chart. 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_heatmap_chart 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.
This server
Across the catalogue