AI agents use set_arrangement_position 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.
This tool creates or modifies design data (pattern arrangement coordinates) within an active CLO3D project. The changes are reversible—positions can be adjusted again or undone—making it a Write operation rather than Destructive. The severity is medium because misuse could corrupt or degrade a design, but the impact is scoped to a single garment project and the changes are recoverable.
From the tool's definition The tool modifies pattern arrangement position parameters (x, y, offset values) in the CLO3D garment design project, which changes the state of the design reversibly.
Attacks that exploit this kind of access
Fine-tune a pattern's arrangement position (x, y, offset from body). 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.
Register the Clo3d MCP server in PolicyLayer and add a rule for set_arrangement_position: 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.
set_arrangement_position 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 set_arrangement_position 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 set_arrangement_position. 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.
set_arrangement_position 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →