This record as markdown: /tools/easehee-rhino-mcp/rhino-mesh-from-brep.md
What rhino_mesh_from_brep does on Rhino
AI agents use rhino_mesh_from_brep 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_mesh_from_brep is rated Medium
The tool creates or generates new mesh geometry from existing Brep objects. While reversible (the original Brep remains and the mesh can be deleted), this is a Write operation as it produces new data objects in the Rhino model. Severity is medium because misuse could clutter or corrupt a user's model with unwanted geometry, but the operation is reversible and doesn't execute arbitrary code or delete data.
From the tool's definition Tool description states 'Mesh a Brep' which creates a new mesh geometry object from a Brep (boundary representation) solid. This is a creation operation that generates new geometric data in Rhino.
Attacks that exploit this kind of access
The rule that runs rhino_mesh_from_brep 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_mesh_from_brep, this is the rule to start with:
rhino_mesh_from_brep 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_mesh_from_brep call is checked against it from then on.
Questions about rhino_mesh_from_brep
Mesh a Brep (bridge only). 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_mesh_from_brep: 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_mesh_from_brep 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_mesh_from_brep 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_mesh_from_brep. 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_mesh_from_brep 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