particles_set_emitting

Toggle whether a GPUParticles2D/3D is emitting in the edited scene (undoable). In-scene and undoable — not gated.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/particles-set-emitting.md

WHAT IT DOES

What particles_set_emitting does on Breakpoint

AI agents use particles_set_emitting to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.

Parameter	Type	Required	Description
`path`	string	Yes	GPUParticles2D/3D node path relative to the scene root
`emitting`	boolean	Yes	Whether the system is emitting

Parameters from the server's own tool schema.

RISK

Why particles_set_emitting is rated Medium

This tool modifies a property (emitting state) of a particle system in the scene. It is explicitly marked as undoable, making it reversible. No code execution, deletion, or financial action is involved — it is a targeted write/update operation on a scene property.

From the tool's definition Toggle whether a GPUParticles2D/3D is emitting in the edited scene (undoable)

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs particles_set_emitting safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For particles_set_emitting, this is the rule to start with:

particles_set_emitting Rate-limited

particles_set_emitting 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "particles_set_emitting": {
      "limits": [
        {
          "counter": "particles_set_emitting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every particles_set_emitting call is checked against it from then on.

FAQ

Questions about particles_set_emitting

What does the particles_set_emitting tool do? +

Toggle whether a GPUParticles2D/3D is emitting in the edited scene (undoable). In-scene and undoable — not gated. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does particles_set_emitting accept? +

particles_set_emitting accepts 2 parameters: path, emitting. Required: path, emitting. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on particles_set_emitting? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for particles_set_emitting: 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 Breakpoint. Nothing to install.

What risk level is particles_set_emitting? +

particles_set_emitting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit particles_set_emitting? +

Yes. Add a rate_limit block to the particles_set_emitting 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.

How do I block particles_set_emitting completely? +

Set action: deny in the PolicyLayer policy for particles_set_emitting. 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.

What MCP server provides particles_set_emitting? +

particles_set_emitting is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →