gh_run_template
Force a fresh solution and (optionally) bake the declared outputs.
This record as markdown: /tools/easehee-rhino-mcp/gh-run-template.md
What gh_run_template does on Rhino
AI agents invoke gh_run_template 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 gh_run_template is rated High
This tool executes a Grasshopper template solution, which runs code/algorithms whose effects depend on the template contents and parameters. While 'bake' operations create geometry (Write-like), the primary action is executing ('Force a fresh solution') a potentially complex algorithmic process.
From the tool's definition Tool description states 'Force a fresh solution and (optionally) bake the declared outputs.' The verb 'Force a fresh solution' indicates execution of a computational workflow in Grasshopper, which can trigger arbitrary geometry operations and modifications in…
Attacks that exploit this kind of access
The rule that runs gh_run_template 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_run_template, this is the rule to start with:
gh_run_template 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 gh_run_template call is checked against it from then on.
Questions about gh_run_template
Force a fresh solution and (optionally) bake the declared outputs. 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 gh_run_template: 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_run_template 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 gh_run_template 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_run_template. 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_run_template 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