rhino_export_obj

Export selected (or all) objects to a Wavefront OBJ file (mesh-only).

SERVERRhino SOURCEeasehee/rhino-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/easehee-rhino-mcp/rhino-export-obj.md

WHAT IT DOES

What rhino_export_obj does on Rhino

AI agents use rhino_export_obj to create or update resources in Rhino, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhino environment.

RISK

Why rhino_export_obj is rated Medium

This tool creates a new file artifact (OBJ format export) from existing 3D model data. It is reversible (the exported file can be deleted or overwritten) and does not modify the source Rhino models or commit irreversible changes. File export operations are Write category rather than Execute because they have deterministic, predictable side effects (file creation) rather than arbitrary code execution.

From the tool's definition Tool description states 'Export selected (or all) objects to a Wavefront OBJ file', which creates/writes a new file output based on Rhino geometry data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rhino_export_obj Rate-limited

rhino_export_obj stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rhino_export_obj": {
      "limits": [
        {
          "counter": "rhino_export_obj_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about rhino_export_obj

What does the rhino_export_obj tool do? +

Export selected (or all) objects to a Wavefront OBJ file (mesh-only). It is categorised as a Write tool in the Rhino MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rhino_export_obj? +

Register the Rhino MCP server in PolicyLayer and add a rule for rhino_export_obj: 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.

What risk level is rhino_export_obj? +

rhino_export_obj is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rhino_export_obj? +

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

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

rhino_export_obj 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.

KEEP EXPLORING

More on Rhino, and thousands of servers like it.

This server

All 245 Rhino tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →