zabbix_delete_discovery_rules

THE RISK

Critical Risk

Why zabbix_delete_discovery_rules needs a policy

The tool permanently removes discovery rules from a Zabbix monitoring system. This is a destructive action that cannot be reversed and would disrupt monitoring infrastructure if executed erroneously. An AI agent misusing this tool could disable critical infrastructure discovery and monitoring capabilities, making it a high-severity destructive operation.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete Low-Level Discovery (LLD) rules from Zabbix' - this is an irreversible deletion operation that cannot be undone.

Documented attack patterns abuse exactly the kind of access zabbix_delete_discovery_rules gives an agent:

POLICY

How to control zabbix_delete_discovery_rules

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_discovery_rules:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "zabbix_delete_discovery_rules"
  ]
}

zabbix_delete_discovery_rules disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Zabbix MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zabbix MCP Server tools

Destructive zabbix_delete_actions Delete actions from Zabbix Destructive zabbix_delete_correlations Delete event correlations from Zabbix Destructive zabbix_delete_dashboards Delete dashboards from Zabbix Destructive zabbix_delete_hostgroups Delete host groups from Zabbix Destructive zabbix_delete_icon_maps Delete icon maps from Zabbix Destructive zabbix_delete_items Delete items from Zabbix Destructive zabbix_delete_maintenance Delete maintenance periods from Zabbix Destructive zabbix_delete_maps Delete network maps from Zabbix

All 102 Zabbix MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Zabbix MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about zabbix_delete_discovery_rules

What does the zabbix_delete_discovery_rules tool do? +

Delete Low-Level Discovery (LLD) rules 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.

How do I enforce a policy on zabbix_delete_discovery_rules? +

Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_delete_discovery_rules: 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.

What risk level is zabbix_delete_discovery_rules? +

zabbix_delete_discovery_rules is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit zabbix_delete_discovery_rules? +

Yes. Add a rate_limit block to the zabbix_delete_discovery_rules 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.

How do I block zabbix_delete_discovery_rules completely? +

Set action: deny in the PolicyLayer policy for zabbix_delete_discovery_rules. 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.

What MCP server provides zabbix_delete_discovery_rules? +

zabbix_delete_discovery_rules 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.

Enforce policy on every Zabbix MCP Server tool call.

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.

CHECK YOUR STACK →