set_particle_velocity_curve
Set a velocity curve for a particle system
This record as markdown: /tools/keeveeg-godot-mcp/set-particle-velocity-curve.md
What set_particle_velocity_curve does on Godot
AI agents use set_particle_velocity_curve 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 |
curve | array | Yes | Curve points |
Parameters from the server's own tool schema.
Why set_particle_velocity_curve is rated Medium
This tool modifies particle system properties (velocity curve) in what is likely a game engine editor or runtime environment. The change is reversible—curves can be updated or reset. It does not execute arbitrary code, delete data, or cause financial impact. However, modifying visual effects parameters could affect rendered output and gameplay behavior, warranting medium severity.
From the tool's definition Tool name 'set_particle_velocity_curve' and description 'Set a velocity curve for a particle system' indicate modification of particle system configuration parameters.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_particle_velocity_curve 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_velocity_curve, this is the rule to start with:
set_particle_velocity_curve 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_velocity_curve call is checked against it from then on.
Questions about set_particle_velocity_curve
Set a velocity curve 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_velocity_curve accepts 2 parameters: path, curve. Required: path, curve. 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_velocity_curve: 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_velocity_curve 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_velocity_curve 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_velocity_curve. 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_velocity_curve 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