AI agents invoke bake_grasshopper_objects to trigger actions in GOLEM-3DMCP-Rhino-. 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.
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…
Documented attack patterns abuse exactly the kind of access bake_grasshopper_objects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GOLEM-3DMCP-Rhino-, and nothing reaches the server without passing your rules. This is the rule we recommend for bake_grasshopper_objects:
{
"version": "1",
"default": "deny",
"tools": {
"bake_grasshopper_objects": {
"limits": [
{
"counter": "bake_grasshopper_objects_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}bake_grasshopper_objects 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.
bake_grasshopper_objects. It is categorised as a Execute tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for bake_grasshopper_objects: 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 GOLEM-3DMCP-Rhino-. Nothing to install.
bake_grasshopper_objects 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 bake_grasshopper_objects 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 bake_grasshopper_objects. 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.
bake_grasshopper_objects is provided by the GOLEM-3DMCP-Rhino- MCP server (thekinghippopotamus/golem-3dmcp-rhino-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GOLEM-3DMCP-Rhino-, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 GOLEM-3DMCP-Rhino- tools catalogued and risk-classified — across an index of 43,000+ MCP servers.