blender.generate_lod
Queue a non-destructive, audited Blender LOD checkpoint for named mesh objects.
This record as markdown: /tools/visionmcp/blender.generate-lod.md
What blender.generate_lod does on Visionmcp
AI agents invoke blender.generate_lod to trigger actions in Visionmcp. 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.generate_lod is rated High
The tool queues a Blender operation (LOD generation) which triggers an external Blender process to run on mesh objects. Although described as 'non-destructive', it executes an external operation whose effects depend on the arguments (which mesh objects to process). It falls under Execute because it triggers external operations, not merely reads data or writes simple structured data reversibly.
From the tool's definition Queue a non-destructive, audited Blender LOD checkpoint for named mesh objects
Attacks that exploit this kind of access
The rule that runs blender.generate_lod safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.generate_lod, this is the rule to start with:
blender.generate_lod 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 Visionmcp, apply this rule, and every blender.generate_lod call is checked against it from then on.
Questions about blender.generate_lod
Queue a non-destructive, audited Blender LOD checkpoint for named mesh objects. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for blender.generate_lod: 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 Visionmcp. Nothing to install.
blender.generate_lod 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.generate_lod 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.generate_lod. 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.generate_lod is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
Across the catalogue