import_project · Clo3d MCP: Risk & Policy

WHAT IT DOES

What import_project does on Clo3d

AI agents use import_project to create or update resources in Clo3d — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clo3d environment.

WHY IT NEEDS A POLICY

Why import_project needs a policy

Importing a project file alters the current working state of the CLO3D scene (overwriting or merging project data). While not permanently destructive or irreversible on the file system, it changes the in-memory scene state, which can override unsaved work. This is a Write operation—it creates/modifies application state reversibly.

From the tool's definition Tool imports/loads files into the CLO3D scene state via 'Open a CLO project or garment file (.zprj/.zpac/.avt) into the scene', which modifies the active scene by replacing or populating it with design data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_project Rate-limited

import_project 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_project": {
      "limits": [
        {
          "counter": "import_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Clo3d, so you can run agents against it safely.

FAQ

Questions about import_project

What does the import_project tool do? +

Open a CLO project or garment file (.zprj/.zpac/.avt) into the scene. It is categorised as a Write tool in the Clo3d MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_project? +

Register the Clo3d MCP server in PolicyLayer and add a rule for import_project: 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. Nothing to install.

What risk level is import_project? +

import_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_project? +

Yes. Add a rate_limit block to the import_project 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.

How do I block import_project completely? +

Set action: deny in the PolicyLayer policy for import_project. 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.

What MCP server provides import_project? +

import_project is provided by the Clo3d MCP server (lilbonner/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.