apply_particle_preset
Apply a predefined particle effect preset
This record as markdown: /tools/keeveeg-godot-mcp/apply-particle-preset.md
What apply_particle_preset does on Godot
AI agents use apply_particle_preset 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 |
preset | string | Yes | Particle preset name |
Parameters from the server's own tool schema.
Why apply_particle_preset is rated Medium
This tool creates or modifies particle effect settings in a Godot project. It is reversible (presets can be changed or removed) and does not execute arbitrary code, delete data, or move money. The sibling tools (add_animation_track, add_audio_bus, add_input_action, etc.) are all Write-category configuration modifications, placing this tool in the same category.
From the tool's definition Tool name 'apply_particle_preset' combined with description 'Apply a predefined particle effect preset' indicates modifying project configuration by applying a preset effect.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs apply_particle_preset 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 apply_particle_preset, this is the rule to start with:
apply_particle_preset 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 apply_particle_preset call is checked against it from then on.
Questions about apply_particle_preset
Apply a predefined particle effect preset. 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.
apply_particle_preset accepts 2 parameters: path, preset. Required: path, preset. 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 apply_particle_preset: 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.
apply_particle_preset 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 apply_particle_preset 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 apply_particle_preset. 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.
apply_particle_preset 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