Critical Risk →

zabbix_delete_scripts

Delete scripts from Zabbix

How to control zabbix_delete_scripts ↓

What zabbix_delete_scripts does on Zabbix MCP Server

AI agents call zabbix_delete_scripts 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.

Critical Risk

Why zabbix_delete_scripts needs a policy

Deletion operations are irreversible and destructive in nature. Removing scripts from a Zabbix monitoring system could break automation, alerting workflows, or monitoring logic that depends on those scripts. This represents an irretrievable loss of configuration data and potential operational disruption. The high severity reflects the broad impact on system functionality if critical scripts are deleted.

From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete scripts from Zabbix'. The verb 'delete' indicates irreversible removal of data.

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

How to control zabbix_delete_scripts

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "zabbix_delete_scripts"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about zabbix_delete_scripts

What does the zabbix_delete_scripts tool do? +

Delete scripts 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_scripts? +

Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_delete_scripts: 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_scripts? +

zabbix_delete_scripts 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_scripts? +

Yes. Add a rate_limit block to the zabbix_delete_scripts 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_scripts completely? +

Set action: deny in the PolicyLayer policy for zabbix_delete_scripts. 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_scripts? +

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

Free to start. No card required.

102 Zabbix MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.