rhino_drawing_section_cut
Cut a section through objects with a plane and place the trace on a sheet (bridge only).
This record as markdown: /tools/easehee-rhino-mcp/rhino-drawing-section-cut.md
What rhino_drawing_section_cut does on Rhino
AI agents invoke rhino_drawing_section_cut 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_drawing_section_cut is rated High
This tool performs a geometric operation (cutting a section) and places results on a sheet. It triggers an external operation in Rhino that modifies the scene/document state. It's not purely read-only, but also not clearly destructive (irreversible deletion). It executes a sectioning and drawing placement operation, making Execute the most appropriate category.
From the tool's definition Cut a section through objects with a plane and place the trace on a sheet
Attacks that exploit this kind of access
The rule that runs rhino_drawing_section_cut 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_drawing_section_cut, this is the rule to start with:
rhino_drawing_section_cut 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_drawing_section_cut call is checked against it from then on.
Questions about rhino_drawing_section_cut
Cut a section through objects with a plane and place the trace on a sheet (bridge only). 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_drawing_section_cut: 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_drawing_section_cut 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_drawing_section_cut 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_drawing_section_cut. 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_drawing_section_cut 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