primitive_mesh_create
Create a PrimitiveMesh resource (box/sphere/cylinder/plane/capsule/prism/torus/quad) and save it to a res:// path. DESTRUCTIVE (writes a file) — gated by confirmation. Assign it with meshinstance_create's 'mesh_path'.
This record as markdown: /tools/breakpoint-mcp/primitive-mesh-create.md
What primitive_mesh_create does on Breakpoint
AI agents use primitive_mesh_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 |
|---|---|---|---|
shape | string | — | box | sphere | cylinder | plane | capsule | prism | torus | quad (default box) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Destination res:// path, e.g. res://meshes/box.tres |
Parameters from the server's own tool schema.
Why primitive_mesh_create is rated Medium
This tool creates and writes a new mesh resource file to disk. While the description mentions 'DESTRUCTIVE,' the actual operation is file creation/writing rather than deletion or overwriting. Since it is 'gated by confirmation,' the reversibility is somewhat mitigated—the file can be deleted afterward.
From the tool's definition Create a PrimitiveMesh resource... and save it to a res:// path. DESTRUCTIVE (writes a file) — gated by confirmation.
Attacks that exploit this kind of access
The rule that runs primitive_mesh_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 primitive_mesh_create, this is the rule to start with:
primitive_mesh_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 primitive_mesh_create call is checked against it from then on.
Questions about primitive_mesh_create
Create a PrimitiveMesh resource (box/sphere/cylinder/plane/capsule/prism/torus/quad) and save it to a res:// path. DESTRUCTIVE (writes a file) — gated by confirmation. Assign it with meshinstance_create's 'mesh_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.
primitive_mesh_create accepts 3 parameters: shape, confirm, to_path. Required: to_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 primitive_mesh_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.
primitive_mesh_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 primitive_mesh_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 primitive_mesh_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.
primitive_mesh_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