distribute_objects
Evenly distribute objects along an axis. If spacing is given, uses fixed spacing.
This record as markdown: /tools/dwgx-blender-copilot/distribute-objects.md
What distribute_objects does on Blender Copilot MCP Server
AI agents use distribute_objects 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 distribute_objects is rated Medium
The tool modifies object positions and spatial layout (Write category), which is a reversible operation. It does not execute arbitrary code, delete data, or trigger financial transactions. Severity is medium because repositioning objects in a 3D scene could affect scene structure and require undo operations if applied incorrectly, but changes are fully reversible in Blender's undo system.
From the tool's definition Tool description states it will 'distribute objects along an axis' with optional 'fixed spacing', indicating modification of object positions/properties in the 3D scene.
Attacks that exploit this kind of access
The rule that runs distribute_objects 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 distribute_objects, this is the rule to start with:
distribute_objects 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 distribute_objects call is checked against it from then on.
Questions about distribute_objects
Evenly distribute objects along an axis. If spacing is given, uses fixed spacing. 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 distribute_objects: 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.
distribute_objects 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 distribute_objects 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 distribute_objects. 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.
distribute_objects 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