delete_drive_file_comment
Permanently delete a comment from a Drive file resolved by filePath or fileId. Provide only one locator. This deletes the comment, not the file.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-drive-file-comment.md
What delete_drive_file_comment does on Huly
AI agents call delete_drive_file_comment 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_file_comment is rated Critical
This tool performs irreversible deletion of user-generated content (a comment). While the blast radius is somewhat limited (a single comment rather than an entire file), deletion is the defining characteristic of the Destructive category, and permanence cannot be undone. The tool sits above Write (reversible modifications) in severity hierarchy.
From the tool's definition 'Permanently delete a comment' - the tool irreversibly removes data (a comment) from a Drive file. The description explicitly states 'This deletes the comment, not the file' to clarify scope, but the action is permanent deletion.
Attacks that exploit this kind of access
The rule that runs delete_drive_file_comment 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_file_comment, this is the rule to start with:
delete_drive_file_comment 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_file_comment call is checked against it from then on.
Questions about delete_drive_file_comment
Permanently delete a comment from a Drive file resolved by filePath or fileId. Provide only one locator. This deletes the comment, not the file. 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_file_comment: 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_file_comment 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_file_comment 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_file_comment. 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_file_comment 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