rhino_turntable_render
Render a turntable sequence (camera orbits around target) to output_dir.
This record as markdown: /tools/easehee-rhino-mcp/rhino-turntable-render.md
What rhino_turntable_render does on Rhino
AI agents invoke rhino_turntable_render to trigger actions in Rhino. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rhino_turntable_render is rated High
This tool executes a rendering process in Rhino, which involves running a compute-intensive operation and writing output image files to a directory. It is an Execute action because it triggers an external operation (rendering engine) whose effects depend on arguments. It also has a Write aspect (files created on disk), but Execute is more severe and better captures the nature of driving Rhino's rendering pipeline.
From the tool's definition 'Render a turntable sequence' and 'camera orbits around target' to 'output_dir' — triggers an external rendering operation that writes files to disk
Attacks that exploit this kind of access
The rule that runs rhino_turntable_render 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_turntable_render, this is the rule to start with:
rhino_turntable_render stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_turntable_render call is checked against it from then on.
Questions about rhino_turntable_render
Render a turntable sequence (camera orbits around target) to output_dir. It is categorised as a Execute tool in the Rhino MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_turntable_render: 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_turntable_render is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rhino_turntable_render 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_turntable_render. 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_turntable_render 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.
Across the catalogue