This record as markdown: /tools/hybridlabor-api-aos/rotate-objects.md
What rotate_objects does on Aos
AI agents use rotate_objects to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why rotate_objects is rated Medium
Based on the tool name and server context (Rhino 3D CAD control), 'rotate_objects' most likely applies a rotation transformation to geometry objects in the scene. This is a reversible modification (objects can be rotated back), placing it in the Write category. Severity is medium as misuse could displace geometry in a design. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'rotate_objects'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs rotate_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 rotate_objects, this is the rule to start with:
rotate_objects stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 rotate_objects call is checked against it from then on.
Questions about rotate_objects
rotate_objects is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for rotate_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 Aos. Nothing to install.
rotate_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rotate_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 rotate_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.
rotate_objects 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