particles_set_process_material
Create a ParticleProcessMaterial and assign it as process_material on a GPUParticles2D/3D in the edited scene (undoable). Optional knobs: gravity [x, y, z], direction [x, y, z], spread, initial_velocity_min/max, scale_min/max, color [r, g, b, a]. GPU particles need a process material to emit. In-...
This record as markdown: /tools/breakpoint-mcp/particles-set-process-material.md
What particles_set_process_material does on Breakpoint
AI agents use particles_set_process_material 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 |
|---|---|---|---|
path | string | Yes | GPUParticles2D/3D node path relative to the scene root |
color | array | — | Base color [r, g, b] or [r, g, b, a] (0..1) |
spread | number | — | Emission spread in degrees |
gravity | array | — | Gravity vector [x, y, z] |
direction | array | — | Emission direction [x, y, z] |
scale_max | number | — | Maximum particle scale |
scale_min | number | — | Minimum particle scale |
initial_velocity_max | number | — | Maximum initial velocity |
initial_velocity_min | number | — | Minimum initial velocity |
Parameters from the server's own tool schema.
Why particles_set_process_material is rated Medium
This tool creates and modifies scene objects (ParticleProcessMaterial assignment) within an editor context. The action is reversible (explicitly marked 'undoable'), making it a Write operation rather than Destructive. While it affects visual rendering in a game/animation scene, it does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Create a ParticleProcessMaterial and assign it as process_material on a GPUParticles2D/3D in the edited scene (undoable)
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs particles_set_process_material 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_set_process_material, this is the rule to start with:
particles_set_process_material 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_set_process_material call is checked against it from then on.
Questions about particles_set_process_material
Create a ParticleProcessMaterial and assign it as process_material on a GPUParticles2D/3D in the edited scene (undoable). Optional knobs: gravity [x, y, z], direction [x, y, z], spread, initial_velocity_min/max, scale_min/max, color [r, g, b, a]. GPU particles need a process material to emit. 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_set_process_material accepts 9 parameters: path, color, spread, gravity, direction, scale_max, scale_min, initial_velocity_max, initial_velocity_min. Required: 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_set_process_material: 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_set_process_material 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_set_process_material 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_set_process_material. 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_set_process_material 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