Delete an OpenSCAD model file from the workspace. The file must exist. Returns the path of the deleted file. Args: name: File name of the model to delete workspace: Directory containing the model. Defaults to the configured temp_dir/models directory. ctx: MCP context for logging Returns: Dict wit...
AI agents call delete_model to permanently remove resources in OpenSCAD 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 files from the workspace without the ability to undo the action. While the blast radius is somewhat limited to the local workspace (not affecting external systems or data), the irreversible nature of file deletion and the potential for an AI agent to inadvertently delete important model files or entire projects classifies this as Destructive.
From the tool's definition Tool description explicitly states 'Delete an OpenSCAD model file from the workspace' and 'Returns the path of the deleted file.' The operation is irreversible file deletion.
Documented attack patterns abuse exactly the kind of access delete_model gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSCAD MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_model:
{
"version": "1",
"default": "deny",
"hide": [
"delete_model"
]
}delete_model disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an OpenSCAD model file from the workspace. The file must exist. Returns the path of the deleted file. Args: name: File name of the model to delete workspace: Directory containing the model. Defaults to the configured temp_dir/models directory. ctx: MCP context for logging Returns: Dict with success status, name, and deleted_path. It is categorised as a Destructive tool in the OpenSCAD MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenSCAD MCP Server MCP server in PolicyLayer and add a rule for delete_model: 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 OpenSCAD MCP Server. Nothing to install.
delete_model 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_model 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_model. 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_model is provided by the OpenSCAD MCP Server MCP server (quellant/openscad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 OpenSCAD MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 OpenSCAD MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.