gh_run

Run the current solution.

SERVERRhino SOURCEeasehee/rhino-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/easehee-rhino-mcp/gh-run.md

WHAT IT DOES

What gh_run does on Rhino

AI agents invoke gh_run 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.

RISK

Why gh_run is rated High

This tool triggers execution of arbitrary Grasshopper scripts/definitions that could perform unpredictable operations on 3D models, file systems, or external integrations. While not inherently destructive without explicit delete operations in the definition, the execution of user-defined workflows with unknown side effects warrants Execute classification.

From the tool's definition Tool name 'gh_run' with description 'Run the current solution' indicates execution of Grasshopper definition code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gh_run 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, this is the rule to start with:

gh_run Rate-limited

gh_run 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gh_run": {
      "limits": [
        {
          "counter": "gh_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every gh_run call is checked against it from then on.

FAQ

Questions about gh_run

What does the gh_run tool do? +

Run the current solution. 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.

How do I enforce a policy on gh_run? +

Register the Rhino MCP server in PolicyLayer and add a rule for gh_run: 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.

What risk level is gh_run? +

gh_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gh_run? +

Yes. Add a rate_limit block to the gh_run 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.

How do I block gh_run completely? +

Set action: deny in the PolicyLayer policy for gh_run. 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.

What MCP server provides gh_run? +

gh_run 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.

KEEP EXPLORING

More on Rhino, and thousands of servers like it.

This server

All 245 Rhino tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →