gh_data_tree_get_batch
Read multiple component outputs in a single bridge round-trip.
This record as markdown: /tools/easehee-rhino-mcp/gh-data-tree-get-batch.md
What gh_data_tree_get_batch does on Rhino
AI agents call gh_data_tree_get_batch to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gh_data_tree_get_batch is rated Low
This tool retrieves data from Grasshopper component outputs in batch. The word 'Read' in the description and the operation of getting/retrieving outputs without any creation, modification, deletion, or execution of external commands clearly places this in the Read category. The batch operation and round-trip optimization do not change the fundamental nature of the action.
From the tool's definition Tool description explicitly states 'Read multiple component outputs' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs gh_data_tree_get_batch 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_get_batch, this is the rule to start with:
gh_data_tree_get_batch is read-only, so it stays allowed. 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_get_batch call is checked against it from then on.
Questions about gh_data_tree_get_batch
Read multiple component outputs in a single bridge round-trip. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.
Register the Rhino MCP server in PolicyLayer and add a rule for gh_data_tree_get_batch: 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_get_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gh_data_tree_get_batch 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_get_batch. 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_get_batch 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