This record as markdown: /tools/easehee-rhino-mcp/rhino-cap-holes.md
What rhino_cap_holes does on Rhino
AI agents use rhino_cap_holes 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_cap_holes is rated Medium
The tool performs a reversible modification of 3D geometry by adding caps to open holes in a Brep. This is a Write operation because it creates or modifies data (adds geometry features) without destroying underlying data structures.
From the tool's definition Tool description: 'Cap all open holes of a Brep' — modifies geometry by capping holes in a Brep (Boundary Representation) object. This is a geometry manipulation operation that alters existing data.
Attacks that exploit this kind of access
The rule that runs rhino_cap_holes 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_cap_holes, this is the rule to start with:
rhino_cap_holes 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_cap_holes call is checked against it from then on.
Questions about rhino_cap_holes
Cap all open holes of a Brep. 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_cap_holes: 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_cap_holes 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_cap_holes 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_cap_holes. 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_cap_holes 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