set_object_layer
Move one or more objects to a different layer.
This record as markdown: /tools/hybridlabor-api-aos/set-object-layer.md
What set_object_layer does on Aos
AI agents use set_object_layer 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 set_object_layer is rated Medium
Moving objects between layers in a CAD application is a reversible metadata/organizational change. The tool modifies object state but does not destroy data (not Destructive), does not execute code (not Execute), and does not involve financial operations (not Financial). This is a typical Write operation that creates or modifies data reversibly.
From the tool's definition Tool name is 'set_object_layer' and description states it will 'Move one or more objects to a different layer.' This modifies object properties (layer assignment) in a reversible manner without deleting data or executing arbitrary code.
Attacks that exploit this kind of access
The rule that runs set_object_layer 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 set_object_layer, this is the rule to start with:
set_object_layer 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 set_object_layer call is checked against it from then on.
Questions about set_object_layer
Move one or more objects to a different layer. 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 set_object_layer: 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.
set_object_layer 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 set_object_layer 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 set_object_layer. 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.
set_object_layer 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