rhino_layer_delete

Delete a layer by name (in standalone mode the layer is hidden + name-prefixed).

SERVERRhino SOURCEeasehee/rhino-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/easehee-rhino-mcp/rhino-layer-delete.md

What rhino_layer_delete does on Rhino

AI agents call rhino_layer_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_layer_delete is rated Critical

This tool irreversibly deletes or hides layers in Rhino, a destructive operation that cannot be undone without undo-stack availability. An AI agent with unsupervised access could permanently remove important design layers, losing work. This is more severe than Write (reversible changes) and meets Destructive criteria: deletion of named objects that users cannot easily recover.

From the tool's definition Tool name 'rhino_layer_delete' explicitly uses 'delete' verb; description states 'Delete a layer by name', confirming irreversible removal of data structure (or permanent hiding in standalone mode with name prefix, making layer inaccessible).

Questions about rhino_layer_delete

What does the rhino_layer_delete tool do? +

Delete a layer by name (in standalone mode the layer is hidden + name-prefixed). 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.

How do I enforce a policy on rhino_layer_delete? +

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

What risk level is rhino_layer_delete? +

rhino_layer_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit rhino_layer_delete? +

Yes. Add a rate_limit block to the rhino_layer_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.

How do I block rhino_layer_delete completely? +

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

What MCP server provides rhino_layer_delete? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rhino's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.