particles_create
Add a GPUParticles2D/3D node under a parent in the edited scene (undoable). Optional initial amount (> 0), lifetime (> 0), emitting. In-scene and undoable — not gated.
This record as markdown: /tools/breakpoint-mcp/particles-create.md
What particles_create does on Breakpoint
AI agents use particles_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 |
|---|---|---|---|
dim | string | — | Dimension: "2d" (default, GPUParticles2D) or "3d" (GPUParticles3D) |
name | string | — | Node name (default "GPUParticles2D"/"GPUParticles3D") |
amount | number | — | Number of particles (> 0, default 8) |
emitting | boolean | — | Whether the system is emitting (default true) |
lifetime | number | — | Particle lifetime in seconds (> 0, default 1) |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why particles_create is rated Medium
This tool creates a new node in the scene graph. It is a reversible write operation (explicitly noted as undoable), so it falls under Write rather than Destructive. Misuse could clutter or corrupt a scene but is recoverable.
From the tool's definition Add a GPUParticles2D/3D node under a parent in the edited scene (undoable)
Attacks that exploit this kind of access
The rule that runs particles_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 particles_create, this is the rule to start with:
particles_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 particles_create call is checked against it from then on.
Questions about particles_create
Add a GPUParticles2D/3D node under a parent in the edited scene (undoable). Optional initial amount (> 0), lifetime (> 0), emitting. 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.
particles_create accepts 6 parameters: dim, name, amount, emitting, lifetime, 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 particles_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.
particles_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 particles_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 particles_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.
particles_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