// SCAN REPORT

GH_mcp_server

12 tools. 8 can modify or destroy data without limits.

8 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

8 can modify or destroy data

4 read-only

12 tools total

Community server · catalogue entry verified 11/06/2026

How to control GH_mcp_server ↓

TOOL MAP

Read (4) Write / Execute (8) Destructive / Financial (0)

MOST DANGEROUS TOOLS

High Risk

Execute · High execute_grasshopper_code This tool directly executes Python code, making it an Execute category tool. Execute · High run_grasshopper_definition This tool executes pre-defined Grasshopper workflows, which are parametric design scripts that can perform arbitrary 3D modeling, geometry generation, and computational operations. Execute · High call_grasshopper_plugin The tool name implies invoking/calling a Grasshopper plugin, which would trigger external operations in Grasshopper/Rhino. Execute · High generate_rhino_code The tool both generates and executes Python code within Rhino, meaning arbitrary code runs on the host system based on a natural language description.

8 of GH_mcp_server's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL GH_MCP_SERVER

PolicyLayer is an MCP gateway — it sits between your AI agents and GH_mcp_server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "add_grasshopper_component": {
    "limits": [
      {
        "counter": "add_grasshopper_component_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_rhino_file": {
    "limits": [
      {
        "counter": "analyze_rhino_file_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GH_mcp_server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GH_MCP_SERVER →

Free to start. No card required.

ALL 12 GH_MCP_SERVER TOOLS

EXECUTE 4 tools

Execute execute_grasshopper_code Execute given Python code. Execute run_grasshopper_definition run_grasshopper_definition Execute call_grasshopper_plugin call_grasshopper_plugin Execute generate_rhino_code Generate and execute Rhino Python code based on a description.

WRITE 4 tools

Write add_grasshopper_component Add a component from an existing Grasshopper plugin. Write connect_grasshopper_components connect_grasshopper_components Write create_parametric_definition create_parametric_definition Write edit_gh_script_component Edit the code in an existing Python script component.

READ 4 tools

Read analyze_rhino_file Analyze a Rhino (.3dm) file. Read extract_geometry Extract geometric data from an existing object. Read list_objects List all objects in a Rhino file. Read measure_distance Measure the distance between two objects in a Rhino file.

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

How do I prevent bulk modifications through GH_mcp_server? +

The GH_mcp_server server has 4 write tools including add_grasshopper_component, connect_grasshopper_components, create_parametric_definition. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GH_mcp_server.

How many tools does the GH_mcp_server MCP server expose? +

12 tools across 3 categories: Execute, Read, Write. 4 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on GH_mcp_server? +

Register the GH_mcp_server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GH_mcp_server tool call.

Deterministic rules across all 12 GH_mcp_server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GH_MCP_SERVER →

Free to start. No card required.

12 GH_mcp_server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

GH_mcp_server

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL GH_MCP_SERVER

// ALL 12 GH_MCP_SERVER TOOLS

// RELATED SERVERS

// FAQ