render_image
Render the scene to an image file. Format is auto-detected from extension
This record as markdown: /tools/dwgx-blender-copilot/render-image.md
What render_image does on Blender Copilot MCP Server
AI agents invoke render_image to trigger actions in Blender Copilot 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.
Why render_image is rated High
Rendering a scene is an active operation that executes Blender's rendering pipeline and writes a file to the filesystem. It is not a simple read or query, but an execution of a compute-intensive process with a side effect (file creation). It does not irreversibly destroy data, so Execute is the most appropriate category.
From the tool's definition 'Render the scene to an image file' — triggers an external rendering operation that writes output to disk
Attacks that exploit this kind of access
The rule that runs render_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_image, this is the rule to start with:
render_image 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every render_image call is checked against it from then on.
Questions about render_image
Render the scene to an image file. Format is auto-detected from extension. It is categorised as a Execute tool in the Blender Copilot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender Copilot MCP Server 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 Blender Copilot MCP Server. 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 Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
Across the catalogue