rhino_object_quantity
Per-object measurement table — one row per object_id with the requested fields.
This record as markdown: /tools/easehee-rhino-mcp/rhino-object-quantity.md
What rhino_object_quantity does on Rhino
AI agents call rhino_object_quantity to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why rhino_object_quantity is rated Low
This tool retrieves measurement data for Rhino objects and returns it in a tabular format. It only reads/queries geometry properties without modifying, creating, or deleting anything. Blast radius is minimal as misuse only results in unnecessary data retrieval.
From the tool's definition Per-object measurement table — one row per object_id with the requested fields
Attacks that exploit this kind of access
The rule that runs rhino_object_quantity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rhino, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino_object_quantity, this is the rule to start with:
rhino_object_quantity 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 Rhino, apply this rule, and every rhino_object_quantity call is checked against it from then on.
Questions about rhino_object_quantity
Per-object measurement table — one row per object_id with the requested fields. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_object_quantity: 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 Rhino. Nothing to install.
rhino_object_quantity 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 rhino_object_quantity 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 rhino_object_quantity. 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.
rhino_object_quantity is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rhino, and thousands of servers like it.
This server
Across the catalogue