explode_object
Explode a polycurve, brep, or group into its component parts.
This record as markdown: /tools/hybridlabor-api-aos/explode-object.md
What explode_object does on Aos
AI agents use explode_object 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 explode_object is rated Medium
The tool transforms a single grouped/compound object into multiple separate objects, which is a structural modification of the CAD model. This is reversible (the parts could be re-grouped), making it Write rather than Destructive. However, it does alter model state and could break workflows if applied incorrectly.
From the tool's definition Tool description: 'Explode a polycurve, brep, or group into its component parts.' This decomposes geometry objects into their constituent elements, modifying the object structure.
Attacks that exploit this kind of access
The rule that runs explode_object 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 explode_object, this is the rule to start with:
explode_object 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 explode_object call is checked against it from then on.
Questions about explode_object
Explode a polycurve, brep, or group into its component parts. 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 explode_object: 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.
explode_object 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 explode_object 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 explode_object. 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.
explode_object 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