Medium Risk

export_glb

Export the garment as a GLB (binary glTF) file.

How to control export_glb ↓

What export_glb does on CLO3D MCP Server

AI agents use export_glb 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.

Medium Risk

Why export_glb needs a policy

Export operations are Write-category because they generate new files/outputs without side effects on the existing project. While export is not Create in the traditional sense, it produces tangible outputs that persist.

From the tool's definition Tool exports data to a file format (GLB/glTF). The operation creates a new output file without reversibly modifying the original CLO3D design—this is data export/serialization rather than design modification or deletion.

Documented attack patterns abuse exactly the kind of access export_glb gives an agent:

How to control export_glb

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 export_glb:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_glb": {
      "limits": [
        {
          "counter": "export_glb_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register CLO3D MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about export_glb

What does the export_glb tool do? +

Export the garment as a GLB (binary glTF) file. 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.

How do I enforce a policy on export_glb? +

Register the CLO3D MCP Server MCP server in PolicyLayer and add a rule for export_glb: 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.

What risk level is export_glb? +

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

Can I rate-limit export_glb? +

Yes. Add a rate_limit block to the export_glb 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 export_glb completely? +

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

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

Enforce policy on every CLO3D MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.