rhino.generate_massing
Generate building massing from the brief and constraints
This record as markdown: /tools/cowork-os/rhino.generate-massing.md
What rhino.generate_massing does on CoWork OS
AI agents invoke rhino.generate_massing to trigger actions in CoWork OS. 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 rhino.generate_massing is rated High
This tool runs a generative algorithm within Rhino to produce 3D building massing geometry. It executes an external operation whose output depends on the provided brief and constraints. It is not purely a read (it creates geometry), but it is not a standard write to a data store — it triggers a computational/modeling process in a CAD environment, placing it in Execute.
From the tool's definition 'Generate building massing from the brief and constraints' — triggers a generative/computational operation in Rhino (3D modeling software) based on input parameters
Attacks that exploit this kind of access
The rule that runs rhino.generate_massing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino.generate_massing, this is the rule to start with:
rhino.generate_massing 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 CoWork OS, apply this rule, and every rhino.generate_massing call is checked against it from then on.
Questions about rhino.generate_massing
Generate building massing from the brief and constraints. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS MCP server in PolicyLayer and add a rule for rhino.generate_massing: 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 CoWork OS. Nothing to install.
rhino.generate_massing 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 rhino.generate_massing 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 rhino.generate_massing. 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.
rhino.generate_massing is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue