SVG 파일로 내보냅니다.
AI agents use export_svg 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 or writes files to persistent storage. While the action itself is reversible (exported files can be deleted or overwritten), it modifies the user's filesystem by creating new files. This is a Write operation rather than Destructive because the export does not irreversibly delete or overwrite existing data—it simply creates new output.
From the tool's definition Tool name is "export_svg" and description states "SVG 파일로 내보냅니다" (exports to SVG file). The tool exports/saves SVG graphics to a file.
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 export_svg: 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.
export_svg 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 export_svg 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 export_svg. 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.
export_svg 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 →