This record as markdown: /tools/hybridlabor-api-aos/apply-transform.md
What apply_transform does on Aos
AI agents invoke apply_transform 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 apply_transform is rated High
In 3D modeling contexts, 'apply_transform' typically moves, rotates, or scales geometry — a Write/Execute operation that modifies object state in the scene. Given the server's stated capability to 'execute arbitrary Python scripts' and 'drive Grasshopper', transforms could trigger broader side effects.
From the tool's definition Tool name 'apply_transform' in a Rhino 3D MCP server context; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs apply_transform 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 apply_transform, this is the rule to start with:
apply_transform 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 apply_transform call is checked against it from then on.
Questions about apply_transform
apply_transform 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 apply_transform: 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.
apply_transform 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 apply_transform 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 apply_transform. 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.
apply_transform 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