gh_component_list

List components currently on the active canvas (optionally filtered).

SERVERRhino SOURCEeasehee/rhino-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What gh_component_list does on Rhino

AI agents call gh_component_list to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gh_component_list is rated Low

This tool performs a read-only operation that queries and returns information about existing components in Grasshopper. It has no side effects—it does not create, modify, delete, or execute operations. The filtered listing capability is still a retrieval operation. The blast radius of misuse is minimal as it only exposes existing component metadata.

From the tool's definition Tool description: 'List components currently on the active canvas (optionally filtered).' The verb 'list' indicates a query operation that retrieves information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gh_component_list Allowed

gh_component_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gh_component_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gh_component_list

What does the gh_component_list tool do? +

List components currently on the active canvas (optionally filtered). It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gh_component_list? +

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

gh_component_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gh_component_list? +

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

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

gh_component_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →