rhino_scatter
Scatter count copies of a source inside a 2-D AABB with optional Z-rotation jitter.
This record as markdown: /tools/easehee-rhino-mcp/rhino-scatter.md
What rhino_scatter does on Rhino
AI agents use rhino_scatter 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 rhino_scatter is rated Medium
This tool creates new geometric objects in Rhino's document space through the scatter operation, which constitutes a write/create action. While the operation is reversible (unlike destructive operations), it modifies the model by adding new geometry. The severity is medium because misuse could clutter a model with many unwanted copies, but the impact is limited in scope and easily undone.
From the tool's definition Tool description states it will "Scatter `count` copies of a source" - this creates new geometry objects in the Rhino 3D model. The action is reversible (objects can be deleted) and modifies the model state by adding new elements.
Attacks that exploit this kind of access
The rule that runs rhino_scatter 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_scatter, this is the rule to start with:
rhino_scatter 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 rhino_scatter call is checked against it from then on.
Questions about rhino_scatter
Scatter count copies of a source inside a 2-D AABB with optional Z-rotation jitter. 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 rhino_scatter: 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_scatter 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 rhino_scatter 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_scatter. 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_scatter 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