패스 빌더를 완료하고 SVG 요소로 추가합니다.
AI agents use path_finish 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/adds a new SVG path element to the canvas, which is a reversible modification of the document. It does not execute arbitrary code, delete data, or cause financial transactions. The blast radius is low because SVG graphics can be easily edited or removed, and this is a standard design operation within a graphics editing context.
From the tool's definition Tool description states 'completes the path builder and adds [it] as an SVG element' — this is a create operation that modifies the SVG canvas state by adding a new graphical element.
Attacks that exploit this kind of access
패스 빌더를 완료하고 SVG 요소로 추가합니다. 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 path_finish: 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.
path_finish 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 path_finish 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 path_finish. 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.
path_finish 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 →