gh_place_slider
Create a Number Slider on the canvas with bounds and initial value.
This record as markdown: /tools/easehee-rhino-mcp/gh-place-slider.md
What gh_place_slider does on Rhino
AI agents use gh_place_slider 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 gh_place_slider is rated Medium
The tool creates (adds) a new parametric slider object to the Grasshopper canvas, which is a reversible Write operation. It does not execute arbitrary code, delete data, or cause financial impact. The blast radius is medium because incorrect slider creation could require cleanup and may affect downstream computations in a Grasshopper definition, but the action itself is easily undone.
From the tool's definition "Create a Number Slider on the canvas" — this action creates a new UI component in Grasshopper with specified parameters (bounds, initial value), modifying the canvas state.
Attacks that exploit this kind of access
The rule that runs gh_place_slider 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_place_slider, this is the rule to start with:
gh_place_slider 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 gh_place_slider call is checked against it from then on.
Questions about gh_place_slider
Create a Number Slider on the canvas with bounds and initial value. 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 gh_place_slider: 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_place_slider 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 gh_place_slider 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_place_slider. 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_place_slider 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