This record as markdown: /tools/cowork-os/blender.render-view.md
What blender.render_view does on CoWork OS
AI agents invoke blender.render_view to trigger actions in CoWork OS. 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 blender.render_view is rated High
Rendering in Blender is an active computational operation that invokes the Blender engine to process a 3D scene and produce output. This is not a passive read; it executes a potentially expensive operation with side effects (output file creation, GPU/CPU usage). It spans Write (creates an image file) and Execute (triggers external process), so Execute is the higher applicable category.
From the tool's definition "Render a camera view to an image" — triggers an external rendering operation in Blender
Attacks that exploit this kind of access
The rule that runs blender.render_view safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.render_view, this is the rule to start with:
blender.render_view 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 CoWork OS, apply this rule, and every blender.render_view call is checked against it from then on.
Questions about blender.render_view
Render a camera view to an image. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS MCP server in PolicyLayer and add a rule for blender.render_view: 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 CoWork OS. Nothing to install.
blender.render_view 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 blender.render_view 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 blender.render_view. 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.
blender.render_view is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue