타원을 그립니다.
AI agents use draw_ellipse 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 new graphical elements (ellipses) within an SVG canvas, which constitutes data creation/modification. It is Write-category because the changes are reversible—ellipses can be removed or modified. There is no code execution, deletion, or financial impact. Severity is low because misuse only affects local SVG rendering with no external side effects or data loss risk.
From the tool's definition Tool name 'draw_ellipse' and description indicate it creates/modifies SVG graphics by drawing elliptical shapes. The server description confirms this is for 'creation and manipulation of professional-grade SVG graphics'.
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 draw_ellipse: 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.
draw_ellipse 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 draw_ellipse 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 draw_ellipse. 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.
draw_ellipse 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 →