create_particles
Create a GPUParticles2D or GPUParticles3D node
This record as markdown: /tools/keeveeg-godot-mcp/create-particles.md
What create_particles does on Godot
AI agents use create_particles 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 |
|---|---|---|---|
type | string | Yes | Dimension type |
parent | string | Yes | Parent node path. Use '' (empty string) to add at scene root, or a node name/path (e.g. 'Player' or 'Player/Sprites') to add as a child of that node. |
properties | object | — | Optional property key-value pairs |
Parameters from the server's own tool schema.
Why create_particles is rated Medium
This tool creates a new particle system node within a Godot project, which is a reversible modification to the scene structure. It does not retrieve data (Read), execute arbitrary code (Execute), delete anything (Destructive), or involve financial transactions (Financial). Creation of scene nodes is a standard Write operation.
From the tool's definition Tool name 'create_particles' and description 'Create a GPUParticles2D or GPUParticles3D node' indicate creation of a new scene node in the Godot game engine.
Attacks that exploit this kind of access
The rule that runs create_particles 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 create_particles, this is the rule to start with:
create_particles 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 create_particles call is checked against it from then on.
Questions about create_particles
Create a GPUParticles2D or GPUParticles3D node. 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.
create_particles accepts 3 parameters: type, parent, properties. Required: type, parent. 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 create_particles: 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.
create_particles 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 create_particles 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 create_particles. 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.
create_particles 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