This record as markdown: /tools/easehee-rhino-mcp/rhino-batch-call.md
What rhino_batch_call does on Rhino
AI agents invoke rhino_batch_call to trigger actions in Rhino. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rhino_batch_call is rated High
The 'batch_call' naming pattern strongly implies executing multiple operations in sequence or bulk. Given the server context (driving Rhino/Grasshopper for geometry creation and manipulation), this likely executes a batch of commands/operations in Rhino. Without a description, exact behavior is unknown, but 'batch' execution of arbitrary operations in a CAD environment carries high misuse potential.
From the tool's definition Tool name 'rhino_batch_call' on a server that drives Rhino 8 and Grasshopper for geometry creation, manipulation, and analysis. Description is empty.
Attacks that exploit this kind of access
The rule that runs rhino_batch_call 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_batch_call, this is the rule to start with:
rhino_batch_call stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_batch_call call is checked against it from then on.
Questions about rhino_batch_call
rhino_batch_call is a execute tool on the Rhino MCP server. It is categorised as a Execute tool in the Rhino MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_batch_call: 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_batch_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rhino_batch_call 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_batch_call. 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_batch_call 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.
Across the catalogue