set_object_name

What set_object_name does on Aos

AI agents use set_object_name 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_name is rated Medium

This is a Write operation because it creates or modifies data reversibly. Assigning names to objects is a non-destructive modification that can be easily undone or overwritten. It has minimal blast radius—worst case being confusion from poor naming conventions. It does not delete data (Destructive), execute code (Execute), trigger financial transactions (Financial), or read-only access (Read).

From the tool's definition The tool performs 'Assign a name to a Rhino object', which modifies metadata of an existing object. Naming is a reversible operation that changes object properties without affecting geometry, data integrity, or triggering external side effects.

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

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

Questions about set_object_name