AI agents use add_seam 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 creates or modifies garment design data (connecting pattern outlines) without irreversibly destroying information. While it affects the garment structure, the change is reversible—seams can be removed or adjusted. This fits the Write category (creates/modifies data reversibly).
From the tool's definition Tool description states it will 'Sew outline line_a of pattern_a to outline line_b of pattern_b,' which modifies the garment design by joining pattern pieces together. This is a reversible change to the CLO3D project data.
Attacks that exploit this kind of access
Sew outline line_a of pattern_a to outline line_b of pattern_b. 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 add_seam: 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.
add_seam 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 add_seam 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 add_seam. 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.
add_seam 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 →