bake_grasshopper_objects

What bake_grasshopper_objects does on Aos

AI agents invoke bake_grasshopper_objects 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 bake_grasshopper_objects is rated High

Baking in Grasshopper is a non-trivial operation that executes the Grasshopper definition and materializes geometry into the Rhino document. This spans Execute (runs Grasshopper computation) and Write (creates new persistent objects). Per the rules, Execute > Write, so Execute is chosen. Severity is high because misuse could flood the document with unintended geometry.

From the tool's definition Tool name 'bake_grasshopper_objects' on a server that 'drives Grasshopper' and 'executes arbitrary Python scripts' — baking in Grasshopper converts parametric geometry into persistent Rhino objects, triggering Grasshopper computation and writing results to…

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bake_grasshopper_objects": {
      "limits": [
        {
          "counter": "bake_grasshopper_objects_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about bake_grasshopper_objects