This record as markdown: /tools/hybridlabor-api-aos/delete-objects.md
What delete_objects does on Aos
AI agents call delete_objects to permanently remove resources in Aos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_objects is rated Critical
Deletion of objects in a Rhino document cannot be undone programmatically through the MCP interface and represents permanent data loss. While Rhino itself has an undo feature, an AI agent invoking this tool in error would cause immediate loss of user work. This fits the Destructive category definition: irreversibly deletes data.
From the tool's definition Tool name is "delete_objects" and description states it will "Delete one or more objects from the Rhino document." This is an irreversible operation that removes data permanently.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_objects, this is the rule to start with:
delete_objects is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every delete_objects call is checked against it from then on.
Questions about delete_objects
Delete one or more objects from the Rhino document. It is categorised as a Destructive tool in the Aos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aos MCP server in PolicyLayer and add a rule for delete_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.
delete_objects is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue