hide_objects

Hide or show objects in the Rhino document.

SERVERAos SOURCE@hybridlabor-api/aos

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/hide-objects.md

WHAT IT DOES

What hide_objects does on Aos

AI agents use hide_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.

RISK

Why hide_objects is rated Medium

Hiding or showing objects modifies the visibility state of objects in the document but does not delete or irreversibly alter geometry. This is a reversible modification (objects can be shown again), placing it in the Write category. Severity is low as no geometry is destroyed and the action is easily undone.

From the tool's definition Hide or show objects in the Rhino document

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hide_objects Rate-limited

hide_objects 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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every hide_objects call is checked against it from then on.

FAQ

Questions about hide_objects

What does the hide_objects tool do? +

Hide or show objects in the Rhino document. 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.

How do I enforce a policy on hide_objects? +

Register the Aos MCP server in PolicyLayer and add a rule for hide_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.

What risk level is hide_objects? +

hide_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hide_objects? +

Yes. Add a rate_limit block to the hide_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.

How do I block hide_objects completely? +

Set action: deny in the PolicyLayer policy for hide_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.

What MCP server provides hide_objects? +

hide_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.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →