rhino_object_move_to_layer
Reassign one or more objects to a different layer (creating it if absent).
This record as markdown: /tools/easehee-rhino-mcp/rhino-object-move-to-layer.md
What rhino_object_move_to_layer does on Rhino
AI agents use rhino_object_move_to_layer to create or update resources in Rhino, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhino environment.
Why rhino_object_move_to_layer is rated Medium
This tool modifies the state of Rhino objects by changing their layer assignment and creates new layers as needed. These are write operations because they alter data structures in the Rhino document, but they are reversible (objects can be moved to different layers, layers can be deleted).
From the tool's definition Tool description states it will 'Reassign one or more objects to a different layer (creating it if absent)' — this modifies object properties (layer assignment) and can create new layers, which are reversible write operations.
Attacks that exploit this kind of access
The rule that runs rhino_object_move_to_layer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rhino, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino_object_move_to_layer, this is the rule to start with:
rhino_object_move_to_layer 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 Rhino, apply this rule, and every rhino_object_move_to_layer call is checked against it from then on.
Questions about rhino_object_move_to_layer
Reassign one or more objects to a different layer (creating it if absent). It is categorised as a Write tool in the Rhino MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_object_move_to_layer: 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 Rhino. Nothing to install.
rhino_object_move_to_layer 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 rhino_object_move_to_layer 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 rhino_object_move_to_layer. 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.
rhino_object_move_to_layer is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rhino, and thousands of servers like it.
This server
Across the catalogue