rhino_bim_pset_delete
Remove every property under a named PropertySet from an object.
This record as markdown: /tools/easehee-rhino-mcp/rhino-bim-pset-delete.md
What rhino_bim_pset_delete does on Rhino
AI agents call rhino_bim_pset_delete to permanently remove resources in Rhino, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why rhino_bim_pset_delete is rated Critical
This tool permanently deletes properties from BIM objects without reversibility. While it targets object metadata rather than entire objects, the irreversible nature of property deletion and the potential loss of important building information data (common in BIM workflows) qualifies this as Destructive rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Remove every property under a named PropertySet from an object.' The verb 'remove' combined with the scope 'every property' indicates irreversible deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rhino_bim_pset_delete 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_bim_pset_delete, this is the rule to start with:
rhino_bim_pset_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_bim_pset_delete call is checked against it from then on.
Questions about rhino_bim_pset_delete
Remove every property under a named PropertySet from an object. It is categorised as a Destructive tool in the Rhino MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_bim_pset_delete: 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_bim_pset_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rhino_bim_pset_delete 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_bim_pset_delete. 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_bim_pset_delete 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