rename_object
Rename an object. Blender may append .001 if the name already exists.
This record as markdown: /tools/dwgx-blender-copilot/rename-object.md
What rename_object does on Blender Copilot MCP Server
AI agents use rename_object 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 rename_object is rated Medium
Renaming is a metadata modification operation that is reversible and non-destructive. It creates no side effects beyond changing a label. This falls clearly under Write (modifies data reversibly) rather than Read (no modification) or Execute/Destructive (no irreversible or external effects). Severity is low because renaming has minimal impact on scene integrity or operations.
From the tool's definition Tool description states 'Rename an object', which modifies object metadata in Blender. The mention of Blender's naming convention (.001 suffix) confirms this affects stored properties reversibly.
Attacks that exploit this kind of access
The rule that runs rename_object 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 rename_object, this is the rule to start with:
rename_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 Blender Copilot MCP Server, apply this rule, and every rename_object call is checked against it from then on.
Questions about rename_object
Rename an object. Blender may append .001 if the name already exists. 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 rename_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 Blender Copilot MCP Server. Nothing to install.
rename_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 rename_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 rename_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.
rename_object 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