Open a file in CLO3D. Supports .zprj, .zpac, .avt, .obj, .fbx formats.
AI agents invoke open_file to trigger actions in CLO3D MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Opening a file triggers an external application action (loading a file into CLO3D), which constitutes executing an operation in an external system. It is not a simple read of data, nor does it delete or modify data, but it does cause a side effect in the CLO3D environment (changing the currently loaded project/state).
From the tool's definition Open a file in CLO3D. Supports .zprj, .zpac, .avt, .obj, .fbx formats.
Documented attack patterns abuse exactly the kind of access open_file 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 open_file:
{
"version": "1",
"default": "deny",
"tools": {
"open_file": {
"limits": [
{
"counter": "open_file_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} open_file stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a file in CLO3D. Supports .zprj, .zpac, .avt, .obj, .fbx formats. It is categorised as a Execute tool in the CLO3D MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CLO3D MCP Server MCP server in PolicyLayer and add a rule for open_file: 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.
open_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_file 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 open_file. 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.
open_file 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.