AI agents use export_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.
Export operations typically create output files or serialize data (Write category). Without an explicit description, confidence is moderate. The tool does not appear to execute arbitrary code (Execute), delete permanently (Destructive), or involve money (Financial).
From the tool's definition Tool named 'export_model' with empty description. Based on sibling tools (create_model, delete_model, render_perspectives) and server context (OpenSCAD 3D modeling), this tool likely writes/exports model data to external formats.
Documented attack patterns abuse exactly the kind of access export_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 export_model:
{
"version": "1",
"default": "deny",
"tools": {
"export_model": {
"limits": [
{
"counter": "export_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_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.
export_model. 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 export_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.
export_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 export_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 export_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.
export_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.