render_still
Render a single frame (still image).
This record as markdown: /tools/dwgx-blender-copilot/render-still.md
What render_still does on Blender Copilot MCP Server
AI agents invoke render_still 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_still is rated High
Rendering a still image is an external operation that runs Blender's rendering engine, consuming resources and writing output to disk. It is not a simple read/write of data but an execution of a complex pipeline. The blast radius is medium: it can consume significant CPU/GPU resources and write files, but is generally reversible by deleting the output.
From the tool's definition 'Render a single frame (still image)' — triggers a rendering operation in Blender, which executes a computational process and produces output files on disk.
Attacks that exploit this kind of access
The rule that runs render_still 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_still, this is the rule to start with:
render_still 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_still call is checked against it from then on.
Questions about render_still
Render a single frame (still image). 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_still: 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_still 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_still 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_still. 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_still 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