Deletes one or more hosts from Zabbix.
AI agents call zabbix_host_delete to permanently remove resources in Zabbix 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 hosts from a Zabbix monitoring system. Host deletion is irreversible and destroys associated monitoring data, historical metrics, and configurations. While not a direct financial impact, losing monitoring infrastructure can have serious operational consequences. This is clearly Destructive rather than Write (which would be reversible modifications).
From the tool's definition Tool name: 'zabbix_host_delete'. Description: 'Deletes one or more hosts from Zabbix.' The verb 'deletes' combined with the scope (one or more hosts) indicates irreversible removal of monitoring infrastructure configuration.
Documented attack patterns abuse exactly the kind of access zabbix_host_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zabbix MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for zabbix_host_delete:
{
"version": "1",
"default": "deny",
"hide": [
"zabbix_host_delete"
]
} zabbix_host_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes one or more hosts from Zabbix. It is categorised as a Destructive tool in the Zabbix MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_host_delete: 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 Zabbix MCP Server. Nothing to install.
zabbix_host_delete 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 zabbix_host_delete 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 zabbix_host_delete. 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.
zabbix_host_delete is provided by the Zabbix MCP Server MCP server (leroylim/zabbix-mcp-server-nodejs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zabbix MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
102 Zabbix MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.