gh_components_search

A read tool on the Rhino MCP server.

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-components-search.md

WHAT IT DOES

What gh_components_search does on Rhino

AI agents call gh_components_search 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_components_search is rated Low

A search function that queries available components is a read-only operation with no side effects. Even though the description is empty, the name and context of sibling tools (list, get, connect, bake) clearly indicate this retrieves information about components rather than creating, executing, or destructing data.

From the tool's definition Tool name 'gh_components_search' indicates a search operation. Sibling tools like 'gh_component_list' and pattern of 'gh_*' commands suggest this retrieves available Grasshopper components without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gh_components_search Allowed

gh_components_search 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_components_search": {}
  }
}

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

FAQ

Questions about gh_components_search

What does the gh_components_search tool do? +

gh_components_search is a read tool on the Rhino MCP server. 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_components_search? +

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

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

Can I rate-limit gh_components_search? +

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

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

gh_components_search 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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