rhino_export_gbxml
Export thermal / structural BIM payload to gbXML (bridge only).
This record as markdown: /tools/easehee-rhino-mcp/rhino-export-gbxml.md
What rhino_export_gbxml does on Rhino
AI agents use rhino_export_gbxml 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.
Why rhino_export_gbxml is rated Medium
This tool creates or writes new data (gbXML exports) which is reversible—exported files can be deleted or regenerated. It does not execute arbitrary code, trigger financial transactions, or irreversibly destroy data.
From the tool's definition Tool exports thermal/structural BIM payload to gbXML format. 'Export' indicates creation and output of data in a specific file format, modifying the file system or external data store.
Attacks that exploit this kind of access
The rule that runs rhino_export_gbxml 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_gbxml, this is the rule to start with:
rhino_export_gbxml 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_export_gbxml call is checked against it from then on.
Questions about rhino_export_gbxml
Export thermal / structural BIM payload to gbXML (bridge 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.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_export_gbxml: 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_export_gbxml is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rhino_export_gbxml 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_export_gbxml. 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_export_gbxml 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