get_object_info
Return full detail for a single Rhino object identified by its GUID.
This record as markdown: /tools/hybridlabor-api-aos/get-object-info.md
What get_object_info does on Aos
AI agents call get_object_info 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.
Why get_object_info is rated Low
This tool retrieves and queries information about a 3D object in Rhino by its unique identifier. It performs no creation, modification, deletion, or execution of code. The operation is read-only and returns data without altering the model state. Severity is low because retrieving object properties poses minimal risk—an agent cannot cause structural damage, financial harm, or irreversible changes through this query.
From the tool's definition Tool name 'get_object_info' and description 'Return full detail for a single Rhino object identified by its GUID' indicates retrieval of object metadata with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_object_info 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_object_info, this is the rule to start with:
get_object_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every get_object_info call is checked against it from then on.
Questions about get_object_info
Return full detail for a single Rhino object identified by its GUID. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for get_object_info: 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.
get_object_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_object_info 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.
Set action: deny in the PolicyLayer policy for get_object_info. 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.
get_object_info 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.
More on Aos, and thousands of servers like it.
This server
Across the catalogue