AI agents invoke run_grasshopper_definition 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.
This tool executes pre-defined Grasshopper workflows, which are parametric design scripts that can perform arbitrary 3D modeling, geometry generation, and computational operations. While the description is empty (lowering confidence slightly), the name combined with sibling tools clearly indicates code/workflow execution.
From the tool's definition Tool name 'run_grasshopper_definition' indicates execution of Grasshopper definitions. Server context shows tools like 'execute_grasshopper_code', 'generate_rhino_code', and 'create_parametric_definition' that suggest code/script execution capabilities.
Documented attack patterns abuse exactly the kind of access run_grasshopper_definition 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 run_grasshopper_definition:
{
"version": "1",
"default": "deny",
"tools": {
"run_grasshopper_definition": {
"limits": [
{
"counter": "run_grasshopper_definition_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_grasshopper_definition 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.
run_grasshopper_definition. 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 run_grasshopper_definition: 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.
run_grasshopper_definition 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 run_grasshopper_definition 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 run_grasshopper_definition. 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.
run_grasshopper_definition 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.