lock_objects

What lock_objects does on Aos

AI agents use lock_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 lock_objects is rated Medium

Locking/unlocking objects in a CAD document is a state modification operation that is reversible and non-destructive. While it affects document state, it does not execute arbitrary operations, delete data, or create irreversible changes. This places it in the Write category. Severity is low because the impact is limited to object accessibility flags with no direct data loss or execution risk.

From the tool's definition Tool description states: "Lock or unlock objects in the Rhino document." This modifies object state (lock/unlock status) but does not delete, execute code, or create financial transactions. The operation is reversible—objects can be unlocked.

The rule that runs lock_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 lock_objects, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lock_objects": {
      "limits": [
        {
          "counter": "lock_objects_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about lock_objects