move_objects
Translate (move) objects by a displacement vector.
This record as markdown: /tools/hybridlabor-api-aos/move-objects.md
What move_objects does on Aos
AI agents use move_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 move_objects is rated Medium
The tool creates or modifies data (object positions) in a reversible manner. It does not delete, destroy, or execute arbitrary code—it performs a geometric transformation. While the server itself can 'execute arbitrary Python scripts,' this specific tool is narrowly scoped to translation operations. The modification is easily undone, placing it in Write rather than Execute or Destructive.
From the tool's definition Tool name is 'move_objects' and description states it will 'Translate (move) objects by a displacement vector.' This modifies object positions in the Rhino model, which is reversible by moving them back or undoing.
Attacks that exploit this kind of access
The rule that runs move_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 move_objects, this is the rule to start with:
move_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 move_objects call is checked against it from then on.
Questions about move_objects
Translate (move) objects by a displacement vector. 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 move_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.
move_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 move_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 move_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.
move_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