render_set_camera
Set the active render camera.
This record as markdown: /tools/dwgx-blender-copilot/render-set-camera.md
What render_set_camera does on Blender Copilot MCP Server
AI agents use render_set_camera to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why render_set_camera is rated Medium
This tool modifies a reversible configuration setting (which camera is active for rendering) without deleting data or executing arbitrary code. While it affects scene output, the change can be undone by setting a different camera. The blast radius is moderate—an AI agent setting an unexpected camera could produce incorrect renders or obscure intended visual output, but this is correctable.
From the tool's definition Tool name 'render_set_camera' and description 'Set the active render camera' indicate modification of render settings by selecting/changing the camera used for rendering.
Attacks that exploit this kind of access
The rule that runs render_set_camera 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_set_camera, this is the rule to start with:
render_set_camera stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_set_camera call is checked against it from then on.
Questions about render_set_camera
Set the active render camera. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for render_set_camera: 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_set_camera is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the render_set_camera 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_set_camera. 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_set_camera 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.
This server
Across the catalogue