Remove a particle system from the scene.
AI agents call deleteParticles to permanently remove resources in Maige 3d — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a particle system, which is an irreversible operation that cannot be undone. This matches the Destructive category definition ('irreversibly deletes or overwrites data, or actions that cannot be undone'). While the blast radius is limited to 3D scene state rather than persistent data or financial systems, deletion without recovery capability warrants Destructive classification.
From the tool's definition Tool name 'deleteParticles' and description 'Remove a particle system from the scene' indicate irreversible deletion of a scene element.
Attacks that exploit this kind of access
Remove a particle system from the scene. It is categorised as a Destructive tool in the Maige 3d MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Maige 3d MCP server in PolicyLayer and add a rule for deleteParticles: 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 Maige 3d. Nothing to install.
deleteParticles is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteParticles 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 deleteParticles. 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.
deleteParticles is provided by the Maige 3d MCP server (m-ai-gexr/mcp-webgpu). 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 →