AI agents call read_particles to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene_path | object | — | Filter to a specific scene |
particle_type | object | — | Filter: GPUParticles3D, CPUParticles3D, GPUParticles2D |
Parameters from the server's own tool schema.
This tool queries or lists existing particle systems in the Godot project without creating, modifying, deleting, or executing any operations. It is a passive data retrieval operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'read_particles' and description 'List particle systems' indicate a retrieval operation with no side effects. The verb 'read' and 'list' are characteristic of Read category tools.
Attacks that exploit this kind of access
List particle systems. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_particles accepts 2 parameters: scene_path, particle_type. 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 read_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.
read_particles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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 read_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.
read_particles is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
read_particles is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →