AI agents use draw_ellipse to create or update resources in Paint MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paint MCP environment.
This tool creates visual content on a drawing canvas by adding an ellipse shape. It modifies the canvas state but does not delete, destroy, execute code, access external systems, or perform financial transactions. The effect is reversible and limited to the scope of the canvas object, making it a Write operation with low severity—misuse would only affect the digital artwork, not cause real-world harm or data loss.
From the tool's definition Tool name 'draw_ellipse' and description 'Draw an ellipse bounded by the rectangle at (x, y) with given size' indicate a drawing operation that creates or modifies canvas state.
Attacks that exploit this kind of access
Draw an ellipse bounded by the rectangle at (x, y) with given size. It is categorised as a Write tool in the Paint MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paint 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 Paint 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 Paint MCP server (joeyballentine/paint-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 →