This record as markdown: /tools/hybridlabor-api-aos/distribute-objects.md
What distribute_objects does on Aos
AI agents use distribute_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 distribute_objects is rated Medium
This tool repositions/moves existing objects in the scene by redistributing them along an axis. It modifies the spatial arrangement of geometry but does not delete or irreversibly destroy data — objects remain intact, just repositioned. This is a reversible Write operation (move/transform), though misuse could displace objects unintentionally.
From the tool's definition Distribute objects evenly along an axis
Attacks that exploit this kind of access
The rule that runs distribute_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 distribute_objects, this is the rule to start with:
distribute_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 distribute_objects call is checked against it from then on.
Questions about distribute_objects
Distribute objects evenly along an axis. 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 distribute_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.
distribute_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 distribute_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 distribute_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.
distribute_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