set_particle_material
Set or create a ParticleProcessMaterial for a particle system
This record as markdown: /tools/keeveeg-godot-mcp/set-particle-material.md
What set_particle_material does on Godot
AI agents use set_particle_material to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Particle node path |
properties | object | Yes | Process material properties (direction, spread, gravity, initial_velocity, etc.) |
Parameters from the server's own tool schema.
Why set_particle_material is rated Medium
This tool creates or modifies particle material configurations in a Godot project, which is reversible through subsequent modifications or deletion. It does not execute arbitrary code, delete data irreversibly, or cause financial transactions. While it affects game rendering, the impact is localized to visual properties and can be easily undone.
From the tool's definition Tool name 'set_particle_material' and description 'Set or create a ParticleProcessMaterial for a particle system' indicate creation or modification of particle system material properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_particle_material safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_particle_material, this is the rule to start with:
set_particle_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 Godot, apply this rule, and every set_particle_material call is checked against it from then on.
Questions about set_particle_material
Set or create a ParticleProcessMaterial for a particle system. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_particle_material accepts 2 parameters: path, properties. Required: path, properties. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for set_particle_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 Godot. Nothing to install.
set_particle_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 set_particle_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 set_particle_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.
set_particle_material is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue