This record as markdown: /tools/wise-agent/blender-render-settings.md
What blender_render_settings does on WISE-Agent
AI agents use blender_render_settings to create or update resources in WISE-Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WISE-Agent environment.
Why blender_render_settings is rated Medium
An AI agent can call blender_render_settings faster than any human can review: one bad instruction and it creates or modifies resources in WISE-Agent by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs blender_render_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WISE-Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_render_settings, this is the rule to start with:
blender_render_settings 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 WISE-Agent, apply this rule, and every blender_render_settings call is checked against it from then on.
Questions about blender_render_settings
Set render parameters. It is categorised as a Write tool in the WISE-Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WISE-Agent MCP server in PolicyLayer and add a rule for blender_render_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 WISE-Agent. Nothing to install.
blender_render_settings 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 blender_render_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 blender_render_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.
blender_render_settings is provided by the WISE-Agent MCP server (qwzx4893-stack/WISE-Agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WISE-Agent, and thousands of servers like it.
This server
Across the catalogue