set_particle_color_gradient
Set a color gradient on a particle system
This record as markdown: /tools/keeveeg-godot-mcp/set-particle-color-gradient.md
What set_particle_color_gradient does on Godot
AI agents use set_particle_color_gradient 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 |
gradient | array | Yes | Gradient color stops |
Parameters from the server's own tool schema.
Why set_particle_color_gradient is rated Medium
This tool modifies particle system configuration in what appears to be a Godot game engine MCP server. It creates or updates particle visual properties (color gradient), which is a reversible change to project data. This is a Write operation rather than Read (queries only), Execute (runs arbitrary code/commands), or Destructive (permanent deletion).
From the tool's definition Tool name 'set_particle_color_gradient' and description 'Set a color gradient on a particle system' indicate modification of particle system properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_particle_color_gradient 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_color_gradient, this is the rule to start with:
set_particle_color_gradient 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_color_gradient call is checked against it from then on.
Questions about set_particle_color_gradient
Set a color gradient on 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_color_gradient accepts 2 parameters: path, gradient. Required: path, gradient. 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_color_gradient: 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_color_gradient 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_color_gradient 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_color_gradient. 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_color_gradient 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