csg_create
Add a CSG node under a parent (undoable). 'shape' selects CSGBox3D (box), CSGSphere3D (sphere), CSGCylinder3D (cylinder), CSGTorus3D (torus), CSGPolygon3D (polygon), CSGMesh3D (mesh), or CSGCombiner3D (combiner). Returns the new node's path.
This record as markdown: /tools/breakpoint-mcp/csg-create.md
What csg_create does on Breakpoint
AI agents use csg_create 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 |
|---|---|---|---|
name | string | — | Node name (defaults to the class name) |
shape | string | — | box | sphere | cylinder | torus | polygon | mesh | combiner (default box) |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why csg_create is rated Medium
The tool creates new CSG (Constructive Solid Geometry) nodes in what appears to be a 3D scene graph structure. This is a reversible modification (explicitly marked as 'undoable') that adds data to the scene without deleting or executing arbitrary code.
From the tool's definition Tool description states 'Add a CSG node under a parent (undoable)' and 'Returns the new node's path'. This creates new scene objects/data that can be reversed via undo.
Attacks that exploit this kind of access
The rule that runs csg_create 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 csg_create, this is the rule to start with:
csg_create 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 csg_create call is checked against it from then on.
Questions about csg_create
Add a CSG node under a parent (undoable). 'shape' selects CSGBox3D (box), CSGSphere3D (sphere), CSGCylinder3D (cylinder), CSGTorus3D (torus), CSGPolygon3D (polygon), CSGMesh3D (mesh), or CSGCombiner3D (combiner). Returns the new node's path. 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.
csg_create accepts 3 parameters: name, shape, parent_path. Required: 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 csg_create: 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.
csg_create 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 csg_create 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 csg_create. 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.
csg_create 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