Delete a cached scene. Cannot delete the 'default' scene this way — use a fresh create_scene call.
AI agents call delete_scene to permanently remove resources in Formlabs Local — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete_scene permanently removes a scene object, which cannot be undone. This is a destructive action that fits the Destructive category (irreversibly deletes data) with high severity because losing scene configuration data in a manufacturing/3D printing context could disrupt workflows. Confidence is high because the name and description unambiguously indicate deletion.
From the tool's definition 'Delete a cached scene' — the tool explicitly performs an irreversible deletion operation on scene data.
Attacks that exploit this kind of access
Delete a cached scene. Cannot delete the 'default' scene this way — use a fresh create_scene call. It is categorised as a Destructive tool in the Formlabs Local MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Formlabs Local MCP server in PolicyLayer and add a rule for delete_scene: 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 Formlabs Local. Nothing to install.
delete_scene 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 delete_scene 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 delete_scene. 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.
delete_scene is provided by the Formlabs Local MCP server (mkebiclioglu/formlabs-local-mcp). 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 →