This record as markdown: /tools/easehee-rhino-mcp/gh-cluster-create.md
What gh_cluster_create does on Rhino
AI agents use gh_cluster_create 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_cluster_create is rated Medium
This tool modifies the Grasshopper workspace by creating named clusters, which organize components but do not execute computations, delete data, or trigger financial transactions. The action is reversible (clusters can be ungrouped), making it a Write operation rather than Execute or Destructive.
From the tool's definition The tool performs a grouping operation that 'creates' a cluster—a reversible organizational modification in Grasshopper. The verb 'group' and 'create' indicate data modification without permanent deletion or external code execution.
Attacks that exploit this kind of access
The rule that runs gh_cluster_create 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_cluster_create, this is the rule to start with:
gh_cluster_create 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_cluster_create call is checked against it from then on.
Questions about gh_cluster_create
Group components into a named cluster. 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_cluster_create: 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_cluster_create 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_cluster_create 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_cluster_create. 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_cluster_create 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