auto_hang · Clo3d MCP: Risk & Policy

WHAT IT DOES

What auto_hang does on Clo3d

AI agents invoke auto_hang to trigger actions in Clo3d. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why auto_hang needs a policy

This tool executes an automated action within CLO3D (auto-hanging a garment), which involves driving an external application to perform a simulation/arrangement operation. It is not purely reading data, nor is it writing/creating new content in a reversible store — it triggers an operational behavior in the 3D environment. The 'bottom=True' parameter variant suggests it controls the execution mode.

From the tool's definition Auto-hang a garment on a hanger — triggers an automated operation in CLO3D that repositions/arranges a garment on a hanger object

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_hang Rate-limited

auto_hang stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auto_hang": {
      "limits": [
        {
          "counter": "auto_hang_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 auto_hang

What does the auto_hang tool do? +

Auto-hang a garment on a hanger. bottom=True uses bottom hangers. It is categorised as a Execute tool in the Clo3d MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auto_hang? +

Register the Clo3d MCP server in PolicyLayer and add a rule for auto_hang: 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 auto_hang? +

auto_hang is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit auto_hang? +

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

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

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