gd_create_particle
AI agents use gd_create_particle to create or update resources in Geometry Dash Mcp Geode — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Geometry Dash Mcp Geode environment.
This tool creates particle effects within Geometry Dash levels, which is a reversible modification to level data. It fits the Write category (creates or modifies data reversibly). Severity is medium because particles are cosmetic/non-critical level components, though creating excessive particles could impact level performance.
From the tool's definition Tool name 'gd_create_particle' and server context indicate creation of Geometry Dash level elements. The 'create' verb strongly suggests data creation. Description is empty, reducing confidence.
Attacks that exploit this kind of access
gd_create_particle. It is categorised as a Write tool in the Geometry Dash Mcp Geode MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Geometry Dash Mcp Geode MCP server in PolicyLayer and add a rule for gd_create_particle: 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 Geometry Dash Mcp Geode. Nothing to install.
gd_create_particle 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 gd_create_particle 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 gd_create_particle. 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.
gd_create_particle is provided by the Geometry Dash Mcp Geode MCP server (noame2289-afk/geometry-dash-mcp-geode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →