particle_start_emitting

A execute tool on the Godot MCP server.

SERVERGodot SOURCEchanceflow/godot-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chanceflow-godot-mcp/particle-start-emitting.md

WHAT IT DOES

What particle_start_emitting does on Godot

AI agents invoke particle_start_emitting to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why particle_start_emitting is rated High

This tool executes an operation that triggers behavior in the Godot game engine (starting particle emissions). While not destructive or financial, it causes state changes and effects that depend on the game context. The empty description reduces confidence slightly, but the name strongly suggests an Execute action.

From the tool's definition Tool name 'particle_start_emitting' indicates it triggers a particle emission action in the Godot engine. The verb 'start' combined with 'emitting' suggests an operation that initiates a process with external effects (particles will render/display in the game…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs particle_start_emitting 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 particle_start_emitting, this is the rule to start with:

particle_start_emitting Rate-limited

particle_start_emitting stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "particle_start_emitting": {
      "limits": [
        {
          "counter": "particle_start_emitting_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about particle_start_emitting

What does the particle_start_emitting tool do? +

particle_start_emitting is a execute tool on the Godot MCP server. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on particle_start_emitting? +

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

What risk level is particle_start_emitting? +

particle_start_emitting is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit particle_start_emitting? +

Yes. Add a rate_limit block to the particle_start_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 particle_start_emitting completely? +

Set action: deny in the PolicyLayer policy for particle_start_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 particle_start_emitting? +

particle_start_emitting is provided by the Godot MCP server (chanceflow/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 84 Godot tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →