gh_connect_components
Create a wire from one component output to another component input.
This record as markdown: /tools/easehee-rhino-mcp/gh-connect-components.md
What gh_connect_components does on Rhino
AI agents use gh_connect_components 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 gh_connect_components is rated Medium
This tool is classified as Write because it creates new connections (wires) in a Grasshopper definition, which reversibly modifies the computational graph. While it alters the state of the design, these changes can be undone (deleted), making it Write rather than Destructive or Execute.
From the tool's definition The tool creates a wire connection between Grasshopper components, which modifies the state of the computational graph.
Attacks that exploit this kind of access
The rule that runs gh_connect_components 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 gh_connect_components, this is the rule to start with:
gh_connect_components 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 gh_connect_components call is checked against it from then on.
Questions about gh_connect_components
Create a wire from one component output to another component input. 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 gh_connect_components: 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.
gh_connect_components 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 gh_connect_components 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 gh_connect_components. 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.
gh_connect_components 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