particles_set_amount
Set the number of particles (amount, > 0) on a GPUParticles2D/3D in the edited scene (undoable). In-scene and undoable — not gated.
This record as markdown: /tools/godot-breakpoint-mcp/particles-set-amount.md
What particles_set_amount does on Godot Breakpoint
AI agents use particles_set_amount to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why particles_set_amount is rated Medium
This tool modifies scene properties (particle count) but the action is undoable, making it a reversible write operation rather than destructive. While it affects visual rendering performance and could be misused to degrade editor performance by setting extremely high particle counts, the impact is limited to the editing session and can be reversed.
From the tool's definition Tool description states it "Set[s] the number of particles" and is explicitly marked "undoable", indicating a reversible modification to scene state. The tool operates on in-scene GPUParticles2D/3D objects in an editing context.
Attacks that exploit this kind of access
The rule that runs particles_set_amount safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For particles_set_amount, this is the rule to start with:
particles_set_amount 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 Breakpoint, apply this rule, and every particles_set_amount call is checked against it from then on.
Questions about particles_set_amount
Set the number of particles (amount, > 0) on a GPUParticles2D/3D in the edited scene (undoable). In-scene and undoable — not gated. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for particles_set_amount: 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 Breakpoint. Nothing to install.
particles_set_amount 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 particles_set_amount 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 particles_set_amount. 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.
particles_set_amount is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue