Remove all user-created objects from the scene and reset default lighting.
AI agents call clearScene 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.
clearScene performs an irreversible bulk deletion operation that cannot be undone through the tool itself. While the severity is 'high' rather than 'critical' (as it affects only a 3D scene rather than production data, financial systems, or user accounts), it is categorically Destructive because the action cannot be reversed and completely wipes user-created content.
From the tool's definition Tool description states 'Remove all user-created objects from the scene' - the verb 'remove' combined with 'all' indicates irreversible deletion of data/scene state.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove all user-created objects from the scene and reset default lighting. 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 clearScene: 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.
clearScene 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 clearScene 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 clearScene. 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.
clearScene 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 →