This record as markdown: /tools/easehee-rhino-mcp/rhino-origin-set.md
What rhino_origin_set does on Rhino
AI agents use rhino_origin_set 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_origin_set is rated Medium
This tool modifies model state (the origin/base point) in a reversible manner. It does not delete data, execute arbitrary code, or cause financial impact. The blast radius is medium because changing the origin could affect coordinate-dependent workflows, but the operation is fully reversible by setting it back to the previous value.
From the tool's definition Tool name 'rhino_origin_set' and description 'Set the model base point' indicate creation or modification of a coordinate system reference point in a CAD model.
Attacks that exploit this kind of access
The rule that runs rhino_origin_set 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_origin_set, this is the rule to start with:
rhino_origin_set 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_origin_set call is checked against it from then on.
Questions about rhino_origin_set
Set the model base point. 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_origin_set: 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_origin_set 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_origin_set 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_origin_set. 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_origin_set 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