rhino_attractor_displace_points
A execute tool on the Rhino MCP server.
This record as markdown: /tools/easehee-rhino-mcp/rhino-attractor-displace-points.md
What rhino_attractor_displace_points does on Rhino
AI agents invoke rhino_attractor_displace_points to trigger actions in Rhino. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rhino_attractor_displace_points is rated High
The description is empty, so classification is based solely on the tool name. The name suggests it displaces (moves/modifies) points using an attractor pattern in Rhino, which implies a geometry manipulation operation. This falls under Execute or Write. Given the context of driving Rhino geometry operations, it likely executes a geometric transformation. Confidence is low due to the empty description.
From the tool's definition Tool name 'rhino_attractor_displace_points' on a server that drives Rhino 8 and Grasshopper for geometry creation, manipulation, and analysis.
Attacks that exploit this kind of access
The rule that runs rhino_attractor_displace_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_attractor_displace_points, this is the rule to start with:
rhino_attractor_displace_points stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_attractor_displace_points call is checked against it from then on.
Questions about rhino_attractor_displace_points
rhino_attractor_displace_points is a execute tool on the Rhino MCP server. It is categorised as a Execute tool in the Rhino MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_attractor_displace_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_attractor_displace_points is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rhino_attractor_displace_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_attractor_displace_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_attractor_displace_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.
Across the catalogue