render_get_settings
Get current render settings — engine, resolution, samples, output, camera.
This record as markdown: /tools/dwgx-blender-copilot/render-get-settings.md
What render_get_settings does on Blender Copilot MCP Server
AI agents call render_get_settings to retrieve information from Blender Copilot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why render_get_settings is rated Low
This tool queries and returns render engine, resolution, samples, output, and camera settings. It performs information retrieval only with no capacity to modify state, execute commands, or trigger external operations. No data is deleted, financial transactions occur, or code is executed. Confidence is high because the description is clear and unambiguous.
From the tool's definition Tool name 'render_get_settings' and description 'Get current render settings' explicitly retrieves configuration data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs render_get_settings 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_get_settings, this is the rule to start with:
render_get_settings is read-only, so it stays allowed. 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_get_settings call is checked against it from then on.
Questions about render_get_settings
Get current render settings — engine, resolution, samples, output, camera. It is categorised as a Read tool in the Blender Copilot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for render_get_settings: 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_get_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the render_get_settings 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_get_settings. 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_get_settings 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