gh_save_file

Save the active Grasshopper definition.

SERVERRhino SOURCEeasehee/rhino-mcp

Medium RISK CLASS

Category Write

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-save-file.md

WHAT IT DOES

What gh_save_file does on Rhino

AI agents use gh_save_file 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.

RISK

Why gh_save_file is rated Medium

The tool creates or modifies a file by saving the current Grasshopper definition state. This is a reversible write operation—the file can be edited or reverted later. It is not destructive (no irreversible deletion), not execute (no arbitrary code execution), and not financial.

From the tool's definition Tool description states 'Save the active Grasshopper definition.' This persists changes to a file, which is a write operation that modifies data on disk.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gh_save_file Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gh_save_file": {
      "limits": [
        {
          "counter": "gh_save_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_save_file call is checked against it from then on.

FAQ

Questions about gh_save_file

What does the gh_save_file tool do? +

Save the active Grasshopper definition. 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.

How do I enforce a policy on gh_save_file? +

Register the Rhino MCP server in PolicyLayer and add a rule for gh_save_file: 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_save_file? +

gh_save_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gh_save_file? +

Yes. Add a rate_limit block to the gh_save_file 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_save_file completely? +

Set action: deny in the PolicyLayer policy for gh_save_file. 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_save_file? +

gh_save_file 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 →

Across the catalogue

save_snapshot on Why Did You Render →save_tags on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →