Update an existing OpenSCAD model file with new content. The file must already exist. Use create_model to create new files. Args: name: File name of the model to update content: New OpenSCAD source code for the model workspace: Directory containing the model. Defaults to the configured temp_dir/m...
AI agents use update_model to create or update resources in OpenSCAD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenSCAD MCP Server environment.
This tool modifies existing data (OpenSCAD model files) in a reversible manner. The update operation changes file content but does not delete or irreversibly destroy data—users can revert changes by updating again with previous content. While this could affect design workflows or computational geometry if maliciously modified, it remains a Write operation rather than Destructive.
From the tool's definition Tool description states 'Update an existing OpenSCAD model file with new content' and accepts 'content: New OpenSCAD source code for the model' as parameters.
Documented attack patterns abuse exactly the kind of access update_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 update_model:
{
"version": "1",
"default": "deny",
"tools": {
"update_model": {
"limits": [
{
"counter": "update_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_model stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing OpenSCAD model file with new content. The file must already exist. Use create_model to create new files. Args: name: File name of the model to update content: New OpenSCAD source code for the model workspace: Directory containing the model. Defaults to the configured temp_dir/models directory. ctx: MCP context for logging Returns: Dict with success status, path, and name of the updated file. It is categorised as a Write tool in the OpenSCAD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenSCAD MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.