막대 차트를 생성합니다.
AI agents use chart_bar to create or update resources in SVG Canvas MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SVG Canvas MCP environment.
Creating a chart is a write operation—it generates new SVG content that can be modified or discarded. It does not execute arbitrary code, delete data, or trigger financial transactions. The blast radius of misuse is minimal since it only produces graphical output within the SVG canvas context. Severity is low because charting operations are non-destructive and have limited operational impact.
From the tool's definition Tool name 'chart_bar' and description indicate creation of bar chart graphics. The broader server context shows this is an SVG graphics manipulation tool for 'creation and manipulation of professional-grade SVG graphics'.
Attacks that exploit this kind of access
막대 차트를 생성합니다. It is categorised as a Write tool in the SVG Canvas MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SVG Canvas MCP server in PolicyLayer and add a rule for chart_bar: 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 SVG Canvas MCP. Nothing to install.
chart_bar 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 chart_bar 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_bar. 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_bar is provided by the SVG Canvas MCP server (kim62210/svg-canvas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →