AI agents use set_fabric_color 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.
The tool creates or modifies design data (fabric color properties) reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). The severity is medium because misuse could alter design work, but changes are easily undone and limited to visual properties without affecting core model integrity or external systems.
From the tool's definition Tool modifies fabric properties ('Set the PBR base color of a fabric'), changing visual attributes of design elements. This is a reversible modification of design data within CLO3D.
Documented attack patterns abuse exactly the kind of access set_fabric_color gives an agent:
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 set_fabric_color:
{
"version": "1",
"default": "deny",
"tools": {
"set_fabric_color": {
"limits": [
{
"counter": "set_fabric_color_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_fabric_color 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.
Free to start. No card required.
Set the PBR base color of a fabric. 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.
Register the CLO3D MCP Server MCP server in PolicyLayer and add a rule for set_fabric_color: 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.
set_fabric_color 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_fabric_color 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_fabric_color. 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_fabric_color 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.
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.