rhino_zebra
Run zebra-stripe surface continuity analysis (bridge required).
This record as markdown: /tools/easehee-rhino-mcp/rhino-zebra.md
What rhino_zebra does on Rhino
AI agents invoke rhino_zebra 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_zebra is rated High
This tool executes a specific geometric analysis algorithm (zebra-stripe continuity analysis) on 3D surfaces within Rhino. While not destructive or creating permanent modifications by itself, it triggers external computation that analyzes geometry based on input parameters. The 'bridge required' notation suggests it communicates with Rhino's runtime environment.
From the tool's definition Tool description states 'Run zebra-stripe surface continuity analysis', indicating active execution of a geometric analysis operation on Rhino/Grasshopper surfaces. The word 'Run' explicitly indicates code/command execution.
Attacks that exploit this kind of access
The rule that runs rhino_zebra 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_zebra, this is the rule to start with:
rhino_zebra 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_zebra call is checked against it from then on.
Questions about rhino_zebra
Run zebra-stripe surface continuity analysis (bridge required). 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_zebra: 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_zebra 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_zebra 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_zebra. 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_zebra 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