gh_delete_component

Remove a component from the canvas.

SERVERRhino SOURCEeasehee/rhino-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What gh_delete_component does on Rhino

AI agents call gh_delete_component to permanently remove resources in Rhino, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why gh_delete_component is rated Critical

The tool explicitly removes/deletes a component from the Grasshopper canvas. Deletion of components can cascade, breaking connections and dependent logic in the graph, and is not easily reversible without an undo history. This fits the Destructive category with high severity given the potential blast radius of removing a key component from a computational design pipeline.

From the tool's definition 'Remove a component from the canvas' — deletion of a canvas component is an irreversible destructive action

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gh_delete_component Hidden

gh_delete_component is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gh_delete_component"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gh_delete_component

What does the gh_delete_component tool do? +

Remove a component from the canvas. It is categorised as a Destructive tool in the Rhino MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gh_delete_component? +

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

gh_delete_component is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gh_delete_component? +

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

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

gh_delete_component 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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →