플로우차트를 생성합니다.
AI agents use diagram_flowchart 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.
This tool creates SVG flowchart diagrams, which are new data artifacts. Creation of graphics is a reversible Write operation—the flowchart can be deleted, modified, or replaced. No code execution, financial transactions, or permanent data destruction occurs. Severity is low because flowcharts are typically non-sensitive design artifacts with minimal blast radius if generated incorrectly by an AI agent.
From the tool's definition Tool name 'diagram_flowchart' and description indicating creation of flowcharts; situated within an SVG Canvas MCP server focused on creating and manipulating graphics. The description in Korean '플로우차트를 생성합니다' translates to 'generates/creates a flowchart'.
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 diagram_flowchart: 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.
diagram_flowchart 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 diagram_flowchart 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 diagram_flowchart. 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.
diagram_flowchart 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 →