AI agents invoke call_grasshopper_plugin to trigger actions in GH_mcp_server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name implies invoking/calling a Grasshopper plugin, which would trigger external operations in Grasshopper/Rhino. Given the server context of executing code and running parametric design tools, this falls under Execute. However, the empty description significantly lowers confidence — it could be a Read or Write operation. The most severe plausible interpretation given sibling tools is Execute.
From the tool's definition Tool name 'call_grasshopper_plugin' combined with sibling tools like 'execute_grasshopper_code' and 'generate_rhino_code' on a server that executes code and interacts with Grasshopper/Rhino.
Documented attack patterns abuse exactly the kind of access call_grasshopper_plugin gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GH_mcp_server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_grasshopper_plugin:
{
"version": "1",
"default": "deny",
"tools": {
"call_grasshopper_plugin": {
"limits": [
{
"counter": "call_grasshopper_plugin_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}call_grasshopper_plugin stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
call_grasshopper_plugin. It is categorised as a Execute tool in the GH_mcp_server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GH_mcp_server MCP server in PolicyLayer and add a rule for call_grasshopper_plugin: 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 GH_mcp_server. Nothing to install.
call_grasshopper_plugin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_grasshopper_plugin 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.
Set action: deny in the PolicyLayer policy for call_grasshopper_plugin. 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.
call_grasshopper_plugin is provided by the GH_mcp_server MCP server (veoery/gh_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 GH_mcp_server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 GH_mcp_server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.