AI agents invoke render_image to trigger actions in Clo3d. 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.
Rendering triggers an external computation operation in CLO3D and writes output image files to disk. It is not a simple read (it produces new files) and is not purely a write of user-provided data — it executes a rendering process. The blast radius is medium: misuse could generate unwanted files or consume resources, but it doesn't delete data or move money.
From the tool's definition Render the current scene to image(s). Returns the saved file path(s).
Attacks that exploit this kind of access
Render the current scene to image(s). Returns the saved file path(s). It is categorised as a Execute tool in the Clo3d MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Clo3d MCP server in PolicyLayer and add a rule for render_image: 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.
render_image 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 render_image 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 render_image. 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.
render_image 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.
render_image is one line of Clo3d's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →