add_named_view

Save the current camera position of a viewport as a named view.

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/add-named-view.md

WHAT IT DOES

What add_named_view does on Aos

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

This tool creates or stores a new named view configuration (camera position) within the Rhino document. It is a reversible Write operation—the named view can be deleted or overwritten later. It does not execute arbitrary code, destroy data, or cause financial impact. The blast radius of misuse is limited to unwanted viewport configurations being stored, which is easily correctable.

From the tool's definition Tool description: 'Save the current camera position of a viewport as a named view.' The verb 'Save' and the action of persisting camera state as a named view constitute data creation/modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_named_view Rate-limited

add_named_view 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": {
    "add_named_view": {
      "limits": [
        {
          "counter": "add_named_view_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 add_named_view call is checked against it from then on.

FAQ

Questions about add_named_view

What does the add_named_view tool do? +

Save the current camera position of a viewport as a named view. 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 add_named_view? +

Register the Aos MCP server in PolicyLayer and add a rule for add_named_view: 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 add_named_view? +

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

Can I rate-limit add_named_view? +

Yes. Add a rate_limit block to the add_named_view 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 add_named_view completely? +

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

add_named_view 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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