AI agents use create_pattern 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.
The tool appears to create garment patterns in CLO3D, which is a reversible design operation (patterns can be modified or deleted later). This falls under Write category rather than Execute because it modifies the design project data structure rather than executing arbitrary code.
From the tool's definition Tool name 'create_pattern' combined with server context of CLO3D garment design software; sibling tools include 'add_fabric', 'add_seam', and 'assign_fabric' which are clearly design operations. No description provided, limiting precision.
Attacks that exploit this kind of access
create_pattern. 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 create_pattern: 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.
create_pattern 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 create_pattern 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 create_pattern. 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.
create_pattern 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 →