현재 캔버스를 템플릿으로 저장합니다.
AI agents use template_save 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 persists a new template artifact (the current canvas state) to storage. This is a Write operation as it creates/modifies data reversibly - templates can be updated or deleted later. It has medium severity because misuse could clutter template storage, create unintended templates, or overwrite existing ones, but the effects are fully reversible and localized to the template system.
From the tool's definition Tool name 'template_save' and description indicating it saves the current canvas as a template - a create/modify operation that stores new data.
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 template_save: 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.
template_save 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 template_save 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 template_save. 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.
template_save 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 →