collisionpolygon_add
Add a CollisionPolygon2D/3D node carrying a polygon under a parent (usually a body) in the edited scene (undoable). points is a 2D outline [[x, y], …] (≥3); for 3D it is extruded along Z by depth. 2D build_mode is solids | segments. In-scene and undoable — not gated.
This record as markdown: /tools/breakpoint-mcp/collisionpolygon-add.md
What collisionpolygon_add does on Breakpoint
AI agents use collisionpolygon_add to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
dim | string | — | Dimension: "2d" (default) or "3d" |
name | string | — | Node name (default "CollisionPolygon2D"/"CollisionPolygon3D") |
depth | number | — | 3D only: extrusion depth along Z (default 1.0) |
points | array | Yes | Polygon outline points [[x, y], …] (≥3); a 2D outline even for 3D |
build_mode | string | — | 2D only: solids (default) or segments |
parent_path | string | Yes | Parent node path (usually a body) relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why collisionpolygon_add is rated Medium
This tool creates and adds a new collision polygon node to a scene, which is a reversible modification (explicitly marked 'undoable'). It does not execute arbitrary code, delete data permanently, or affect financial systems. It falls squarely into the Write category as it creates new data structures in the scene.
From the tool's definition The tool description states it will 'Add a CollisionPolygon2D/3D node' and 'in the edited scene (undoable)'. This is a creation operation that modifies the scene by adding a new node.
Attacks that exploit this kind of access
The rule that runs collisionpolygon_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For collisionpolygon_add, this is the rule to start with:
collisionpolygon_add 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every collisionpolygon_add call is checked against it from then on.
Questions about collisionpolygon_add
Add a CollisionPolygon2D/3D node carrying a polygon under a parent (usually a body) in the edited scene (undoable). points is a 2D outline [[x, y], …] (≥3); for 3D it is extruded along Z by depth. 2D build_mode is solids | segments. In-scene and undoable — not gated. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
collisionpolygon_add accepts 6 parameters: dim, name, depth, points, build_mode, parent_path. Required: points, parent_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for collisionpolygon_add: 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 Breakpoint. Nothing to install.
collisionpolygon_add 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 collisionpolygon_add 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 collisionpolygon_add. 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.
collisionpolygon_add is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue