This record as markdown: /tools/aryeon0228-blendermcp/move-object.md
What move_object does on BlenderMCP
AI agents use move_object to create or update resources in BlenderMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
Why move_object is rated Medium
Moving an object changes its position in the scene, which is a reversible modification (the object can be moved back). This is a Write operation as it modifies existing data without destroying it. The blast radius is medium since misuse could displace objects in a 3D scene, requiring manual correction, but the scene is not irreversibly destroyed.
From the tool's definition Move an object to a new location
Attacks that exploit this kind of access
The rule that runs move_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BlenderMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_object, this is the rule to start with:
move_object 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 BlenderMCP, apply this rule, and every move_object call is checked against it from then on.
Questions about move_object
Move an object to a new location. It is categorised as a Write tool in the BlenderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for move_object: 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 BlenderMCP. Nothing to install.
move_object 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 move_object 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 move_object. 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.
move_object is provided by the Blender MCP server (aryeon0228/blendermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
This server
Across the catalogue