Delete/uninstall a plugin by type.
AI agents call delete_plugin 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.
Deleting a plugin removes system functionality permanently and cannot be undone by the tool itself. This constitutes a destructive action with potential to break smart home automations, integrations, or device control. While not financial or system-wide deletion, it represents significant irreversible data/functionality loss in the HC3 ecosystem.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete/uninstall a plugin' — this is an irreversible removal action. Plugins are core components of a smart home system that manage functionality, automations, or integrations.
Attacks that exploit this kind of access
Delete/uninstall a plugin by type. 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_plugin: 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_plugin 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_plugin 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_plugin. 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_plugin 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.
delete_plugin is one line of HC3 MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →