rhino_get_control_points
Get all control points (and weights) of a NURBS curve or surface.
This record as markdown: /tools/easehee-rhino-mcp/rhino-get-control-points.md
What rhino_get_control_points does on Rhino
AI agents call rhino_get_control_points 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_get_control_points is rated Low
This tool retrieves geometric data (control points and weights) from existing NURBS objects in Rhino. It performs a query/fetch operation without creating, modifying, deleting, or executing external operations. The data returned is purely informational and does not alter the model state. This is a Read category tool with low severity since misuse would only expose geometric metadata without causing harm.
From the tool's definition Tool name is 'rhino_get_control_points' and description states it 'Get all control points (and weights) of a NURBS curve or surface' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs rhino_get_control_points 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_get_control_points, this is the rule to start with:
rhino_get_control_points 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_get_control_points call is checked against it from then on.
Questions about rhino_get_control_points
Get all control points (and weights) of a NURBS curve or surface. 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_get_control_points: 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_get_control_points 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_get_control_points 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_get_control_points. 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_get_control_points 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