create_particle_effect
Build a custom additive particle effect from raw params (ParticleEffect + cone emitter + sprite renderer). Use this when the spawn_particle presets aren
This record as markdown: /tools/sbox/create-particle-effect.md
What create_particle_effect does on Sbox
AI agents use create_particle_effect to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why create_particle_effect is rated Medium
This tool creates a new particle effect in the s&box game engine. It is a Write operation as it generates new content (a ParticleEffect with emitter and renderer components) within the game project. It does not execute code, delete data, or involve financial transactions. Misuse could clutter the project with unwanted assets but is reversible, warranting medium severity.
From the tool's definition 'Build a custom additive particle effect from raw params (ParticleEffect + cone emitter + sprite renderer)' — creates a new particle effect asset/object in the game engine
Attacks that exploit this kind of access
The rule that runs create_particle_effect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_particle_effect, this is the rule to start with:
create_particle_effect 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 Sbox, apply this rule, and every create_particle_effect call is checked against it from then on.
Questions about create_particle_effect
Build a custom additive particle effect from raw params (ParticleEffect + cone emitter + sprite renderer). Use this when the spawn_particle presets aren. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for create_particle_effect: 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 Sbox. Nothing to install.
create_particle_effect 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 create_particle_effect 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 create_particle_effect. 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.
create_particle_effect is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue