Import a file into CLO3D. Auto-detects type from extension (.zprj, .zpac, .obj, .fbx, .avt, etc.).
AI agents use import_file to create or update resources in CLO3D MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CLO3D MCP Server environment.
Import operations reversibly add or load data into an application's working state. This is a Write operation rather than Read because it modifies the project/scene state in CLO3D, not merely queries existing data. Severity is medium because a malicious import could introduce malformed geometry or embedded scripts, but the effect is containable by closing the project without saving.
From the tool's definition Tool performs import operation that creates or modifies the CLO3D project state by loading external files (.zprj, .zpac, .obj, .fbx, .avt, etc.) into the application.
Documented attack patterns abuse exactly the kind of access import_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CLO3D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for import_file:
{
"version": "1",
"default": "deny",
"tools": {
"import_file": {
"limits": [
{
"counter": "import_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_file 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.
Import a file into CLO3D. Auto-detects type from extension (.zprj, .zpac, .obj, .fbx, .avt, etc.). It is categorised as a Write tool in the CLO3D MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CLO3D MCP Server MCP server in PolicyLayer and add a rule for import_file: 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 CLO3D MCP Server. Nothing to install.
import_file 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 import_file 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 import_file. 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.
import_file is provided by the CLO3D MCP Server MCP server (ubani-studio/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CLO3D MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 CLO3D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.