This record as markdown: /tools/easehee-rhino-mcp/gh-data-tree-set.md
What gh_data_tree_set does on Rhino
AI agents use gh_data_tree_set 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_data_tree_set is rated Medium
This tool writes data (a DataTree) into a Grasshopper component's input, modifying the state of the Grasshopper document. It is reversible (the value can be changed or cleared), so Write is the appropriate category rather than Destructive. Misuse could corrupt a Grasshopper graph's data flow but is generally recoverable.
From the tool's definition 'Push a DataTree into a component input' — sets/writes data to a component's input parameter in Grasshopper
Attacks that exploit this kind of access
The rule that runs gh_data_tree_set 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_data_tree_set, this is the rule to start with:
gh_data_tree_set 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_data_tree_set call is checked against it from then on.
Questions about gh_data_tree_set
Push a DataTree into a 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_data_tree_set: 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_data_tree_set 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_data_tree_set 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_data_tree_set. 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_data_tree_set 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