Clear all objects from the scene
AI agents call scene_clear to permanently remove resources in 3D MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes all objects without a stated undo capability or recovery mechanism. While the blast radius is limited to the current 3D scene session (not system-wide or financial), the irreversible nature of clearing all objects classifies it as Destructive rather than Write. An AI agent invoking this without explicit user intent could cause loss of significant modeling work.
From the tool's definition Tool name 'scene_clear' with description 'Clear all objects from the scene' indicates irreversible deletion of all 3D models in the current working scene.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all objects from the scene. It is categorised as a Destructive tool in the 3D MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 3D MCP Server MCP server in PolicyLayer and add a rule for scene_clear: 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 3D MCP Server. Nothing to install.
scene_clear 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 scene_clear 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 scene_clear. 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.
scene_clear is provided by the 3D MCP Server MCP server (jagjerez-org/3d-mcp-server). 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 →