AI agents call zabbix_delete_users 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.
Deleting users is a destructive action that cannot be undone. User accounts removal is permanent data loss affecting authentication, permissions, and audit trails. This action modifies the security posture of the system irreversibly. While not as severe as dropping entire databases, it ranks higher than Write operations (create/update) due to the irreversibility and the sensitive nature of user management.
From the tool's definition Tool name is 'zabbix_delete_users' and description states 'Delete users from Zabbix'. The verb 'delete' combined with user account deletion is irreversible.
Documented attack patterns abuse exactly the kind of access zabbix_delete_users 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_delete_users:
{
"version": "1",
"default": "deny",
"hide": [
"zabbix_delete_users"
]
} zabbix_delete_users 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.
Delete users 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_delete_users: 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_delete_users 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_delete_users 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_delete_users. 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_delete_users 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.