This record as markdown: /tools/easehee-rhino-mcp/gh-set-slider.md
What gh_set_slider does on Rhino
AI agents use gh_set_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_set_slider is rated Medium
This tool modifies component parameters in Grasshopper, which is a reversible state change (the slider value can be set to a different value later). It does not delete data, execute arbitrary code, or trigger financial transactions. While it affects geometry computation downstream, the action itself is a parameter modification (Write category).
From the tool's definition Tool description states 'Set a Number Slider component to a numeric value' — this modifies the state of a Grasshopper component parameter.
Attacks that exploit this kind of access
The rule that runs gh_set_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_set_slider, this is the rule to start with:
gh_set_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_set_slider call is checked against it from then on.
Questions about gh_set_slider
Set a Number Slider component to a numeric 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_set_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_set_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_set_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_set_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_set_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