Draw a circle/ellipse (outline or filled). Supports two modes: bounding box (x0,y0,x1,y1) or center+radius (centerX,centerY,radiusX,radiusY).
AI agents use draw_circle to create or update resources in Piskel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Piskel MCP Server environment.
This tool modifies the visual content of a pixel art project reversibly—the circle can be edited, cleared, or undone as part of normal pixel art workflow. It does not execute arbitrary code, delete data irreversibly, or trigger external side effects. The blast radius of misuse is limited to the scope of the current pixel art project's visual state, making it a Write operation with low severity.
From the tool's definition Tool creates or modifies pixel art data by drawing a circle/ellipse within an existing project. Description states it 'Draw[s] a circle/ellipse (outline or filled)' with configurable parameters, and it is part of a pixel art manipulation suite alongside other…
Documented attack patterns abuse exactly the kind of access draw_circle gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Piskel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for draw_circle:
{
"version": "1",
"default": "deny",
"tools": {
"draw_circle": {
"limits": [
{
"counter": "draw_circle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}draw_circle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Draw a circle/ellipse (outline or filled). Supports two modes: bounding box (x0,y0,x1,y1) or center+radius (centerX,centerY,radiusX,radiusY). It is categorised as a Write tool in the Piskel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Piskel MCP Server MCP server in PolicyLayer and add a rule for draw_circle: 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 Piskel MCP Server. Nothing to install.
draw_circle 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_circle 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_circle. 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_circle is provided by the Piskel MCP Server MCP server (yafeiaa/piskel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Piskel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Piskel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.