This record as markdown: /tools/hybridlabor-api-aos/scale-objects-1d.md
What scale_objects_1d does on Aos
AI agents invoke scale_objects_1d 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 scale_objects_1d is rated High
This tool executes a geometric transformation (1D scaling) on objects in Rhino 8. While the description is empty, the server context and sibling tools confirm that this MCP server provides programmatic control to run operations on CAD geometry.
From the tool's definition The tool is part of a server that 'execute[s] arbitrary Python scripts' and provides 'direct, programmatic control of Rhino 8.' The tool name 'scale_objects_1d' indicates it modifies geometry by scaling in one dimension.
Attacks that exploit this kind of access
The rule that runs scale_objects_1d 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 scale_objects_1d, this is the rule to start with:
scale_objects_1d 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 scale_objects_1d call is checked against it from then on.
Questions about scale_objects_1d
scale_objects_1d is a execute tool on the Aos MCP server. 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 scale_objects_1d: 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.
scale_objects_1d 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 scale_objects_1d 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 scale_objects_1d. 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.
scale_objects_1d 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