Delete a QuickApp source file. Note: main files cannot be deleted.
AI agents call delete_quickapp_file to permanently remove resources in HC3 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes QuickApp source files from the HC3 system without the ability to undo the action. While the note that 'main files cannot be deleted' provides some safeguard, the core functionality is destructive as it irreversibly deletes developer code and configuration. This constitutes the most severe category (Destructive > Execute > Write > Read) due to the inability to recover deleted files.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete a QuickApp source file', indicating irreversible removal of data.
Attacks that exploit this kind of access
Delete a QuickApp source file. Note: main files cannot be deleted. It is categorised as a Destructive tool in the HC3 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for delete_quickapp_file: 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 HC3 MCP Server. Nothing to install.
delete_quickapp_file 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_quickapp_file 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_quickapp_file. 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_quickapp_file is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →