rhino_render_to_file
Execute the configured render and write the result to output_path.
This record as markdown: /tools/easehee-rhino-mcp/rhino-render-to-file.md
What rhino_render_to_file does on Rhino
AI agents invoke rhino_render_to_file 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_render_to_file is rated High
This tool both executes a rendering operation (triggering external compute in Rhino) and writes a file to disk at a caller-specified path. The most severe applicable category is Execute, since it runs an external operation whose effects depend on arguments. The ability to write to arbitrary file paths raises the severity to high, as a misused path could overwrite important files.
From the tool's definition 'Execute the configured render and write the result to output_path' — triggers an external rendering operation and writes output to a file path
Attacks that exploit this kind of access
The rule that runs rhino_render_to_file 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_render_to_file, this is the rule to start with:
rhino_render_to_file 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_render_to_file call is checked against it from then on.
Questions about rhino_render_to_file
Execute the configured render and write the result to output_path. 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_render_to_file: 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_render_to_file 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_render_to_file 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_render_to_file. 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_render_to_file 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