This record as markdown: /tools/easehee-rhino-mcp/rhino-weld-mesh.md
What rhino_weld_mesh does on Rhino
AI agents use rhino_weld_mesh 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_weld_mesh is rated Medium
Welding vertices is a reversible modification operation that changes the mesh topology and geometry. It does not delete or irreversibly destroy data (Destructive), does not execute arbitrary code or external operations (Execute), and clearly modifies rather than merely reads geometry (Write).
From the tool's definition Tool name is 'rhino_weld_mesh' and description states it 'Weld coincident vertices in a mesh' — this modifies mesh geometry by merging vertices, altering the underlying data structure.
Attacks that exploit this kind of access
The rule that runs rhino_weld_mesh 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_weld_mesh, this is the rule to start with:
rhino_weld_mesh 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_weld_mesh call is checked against it from then on.
Questions about rhino_weld_mesh
Weld coincident vertices in a mesh. 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_weld_mesh: 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_weld_mesh 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_weld_mesh 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_weld_mesh. 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_weld_mesh 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