delete_drive
Permanently delete an empty Huly Drive space. The Drive must contain no files or folders; non-empty Drives fail with child count and item summaries. This is permanent deletion, not archive or trash.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-drive.md
What delete_drive does on Huly
AI agents call delete_drive to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_drive is rated Critical
This tool irreversibly deletes data (a Huly Drive space) with no undo capability. While it requires the Drive to be empty, the permanent deletion of a storage space and its associated metadata constitutes a destructive action that cannot be recovered. This falls clearly into the Destructive category, which ranks above Execute, Write, and Read.
From the tool's definition Tool description explicitly states "Permanently delete" and "This is permanent deletion, not archive or trash." The tool name is "delete_drive" indicating an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_drive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_drive, this is the rule to start with:
delete_drive 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 Huly, apply this rule, and every delete_drive call is checked against it from then on.
Questions about delete_drive
Permanently delete an empty Huly Drive space. The Drive must contain no files or folders; non-empty Drives fail with child count and item summaries. This is permanent deletion, not archive or trash. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for delete_drive: 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 Huly. Nothing to install.
delete_drive 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 delete_drive 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 delete_drive. 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.
delete_drive is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
Across the catalogue