텍스트 워터마크를 현재 캔버스에 적용합니다.
AI agents use watermark_text 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.
Adding a watermark is a write operation because it modifies the canvas state reversibly. The user or an AI agent can remove or modify the watermark later. It does not execute arbitrary code, destroy data, move money, or perform irreversible actions. The severity is low because watermarks are benign visual overlays with minimal blast radius—the worst case is unwanted visual marking of a design, which is easily undone.
From the tool's definition The tool name is 'watermark_text' and description states it 'applies a text watermark to the current canvas' (translated from Korean: '텍스트 워터마크를 현재 캔버스에 적용합니다').
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 watermark_text: 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.
watermark_text 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 watermark_text 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 watermark_text. 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.
watermark_text 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 →