This record as markdown: /tools/hybridlabor-api-aos/close-grasshopper-definition.md
What close_grasshopper_definition does on Aos
AI agents invoke close_grasshopper_definition to trigger actions in Aos. 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.
Why close_grasshopper_definition is rated High
Closing a Grasshopper definition is an external operation that affects the state of a running Grasshopper/Rhino session. It is not a simple read, and while it doesn't delete data permanently, it terminates an active computational definition which may halt ongoing parametric processes. This is an Execute-category action as it triggers an external operation in Rhino's environment.
From the tool's definition Close a Grasshopper definition that was previously opened
Attacks that exploit this kind of access
The rule that runs close_grasshopper_definition safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_grasshopper_definition, this is the rule to start with:
close_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every close_grasshopper_definition call is checked against it from then on.
Questions about close_grasshopper_definition
Close a Grasshopper definition that was previously opened. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for close_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 Aos. Nothing to install.
close_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 close_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 close_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.
close_grasshopper_definition is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue