rhino_place_grid
Replicate a source object on a count_x x count_y grid with given spacing.
This record as markdown: /tools/easehee-rhino-mcp/rhino-place-grid.md
What rhino_place_grid does on Rhino
AI agents use rhino_place_grid 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_place_grid is rated Medium
The tool creates multiple copies of a geometry object arranged in a grid pattern. This is a reversible modification operation (objects can be deleted) that adds data to the Rhino model without executing arbitrary code or causing irreversible destruction. It falls squarely into the Write category.
From the tool's definition Tool description states 'Replicate a source object on a count_x x count_y grid' — this creates new geometric objects in Rhino via replication/duplication, which modifies the model state.
Attacks that exploit this kind of access
The rule that runs rhino_place_grid 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_place_grid, this is the rule to start with:
rhino_place_grid 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_place_grid call is checked against it from then on.
Questions about rhino_place_grid
Replicate a source object on a count_x x count_y grid with given spacing. 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_place_grid: 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_place_grid 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_place_grid 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_place_grid. 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_place_grid 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