delete_drive_item
Permanently delete a Drive item, meaning a file or folder. Files are deleted with their version records. Folders must be empty; non-empty folders fail with child count and child summaries. This is permanent deletion, not archive or trash.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-drive-item.md
What delete_drive_item does on Huly
AI agents call delete_drive_item 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_item is rated Critical
This tool irreversibly deletes data (files and folder structures) without recovery options. It cannot be undone and represents permanent data loss. This is a canonical Destructive action. Severity is high because unintended deletion of drive items could cause significant organizational data loss, though impact depends on what files are targeted.
From the tool's definition Tool name is 'delete_drive_item' and description states: 'Permanently delete a Drive item' and 'This is permanent deletion, not archive or trash.' The description explicitly emphasizes irreversibility and scope (files with version records, folders with…
Attacks that exploit this kind of access
The rule that runs delete_drive_item 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_item, this is the rule to start with:
delete_drive_item 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_item call is checked against it from then on.
Questions about delete_drive_item
Permanently delete a Drive item, meaning a file or folder. Files are deleted with their version records. Folders must be empty; non-empty folders fail with child count and child 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_item: 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_item 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_item 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_item. 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_item 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