Draws a polygon at the current brush position
AI agents invoke draw_polygon to trigger actions in Open Brush MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation in the Open Brush 3D painting software, causing it to render/draw a polygon. It's not a simple data write to a database but rather triggers a real-time graphical action in an external application. Misuse could result in unwanted content being drawn in an active scene, but the effect is reversible (can be undone), keeping severity at medium.
From the tool's definition 'Draws a polygon at the current brush position' — triggers an external drawing operation in Open Brush via HTTP API
Attacks that exploit this kind of access
Draws a polygon at the current brush position. It is categorised as a Execute tool in the Open Brush MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Open Brush MCP Server MCP server in PolicyLayer and add a rule for draw_polygon: 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 Open Brush MCP Server. Nothing to install.
draw_polygon is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the draw_polygon 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_polygon. 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_polygon is provided by the Open Brush MCP Server MCP server (moz411/openbrush-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 →