get_selected_objects

Return all currently selected objects in the Rhino viewport.

SERVERAos SOURCE@hybridlabor-api/aos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_selected_objects does on Aos

AI agents call get_selected_objects to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_selected_objects is rated Low

This tool queries and returns data about the current state of Rhino (which objects are selected) with no side effects, modifications, code execution, or irreversible actions. It is a pure read operation that retrieves information from the application state.

From the tool's definition Tool name 'get_selected_objects' and description 'Return all currently selected objects in the Rhino viewport' indicate retrieval of viewport state without modification or execution of operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_selected_objects Allowed

get_selected_objects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_selected_objects": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_selected_objects

What does the get_selected_objects tool do? +

Return all currently selected objects in the Rhino viewport. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_selected_objects? +

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

get_selected_objects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_selected_objects? +

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

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

get_selected_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →