Export a tech pack with JSON metadata and images.
AI agents use export_tech_pack 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.
This tool generates and writes new deliverable files (tech pack with JSON metadata and images) to disk or export location. While not destructive and not modifying existing core design data irreversibly, it creates new data artifacts. The blast radius is medium: an agent could export sensitive design information, create large files, or spam exports, but the operation is reversible (exported files can be deleted).
From the tool's definition Tool creates and exports a tech pack with JSON metadata and images, which involves generating new files and data artifacts. The term 'export' combined with file generation (metadata + images) constitutes data creation/writing rather than simple retrieval.
Documented attack patterns abuse exactly the kind of access export_tech_pack 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 export_tech_pack:
{
"version": "1",
"default": "deny",
"tools": {
"export_tech_pack": {
"limits": [
{
"counter": "export_tech_pack_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_tech_pack 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.
Export a tech pack with JSON metadata and images. 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 export_tech_pack: 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.
export_tech_pack 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 export_tech_pack 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 export_tech_pack. 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.
export_tech_pack 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.