Critical Risk →

zabbix_delete_proxies

Delete proxies from Zabbix

How to control zabbix_delete_proxies ↓

What zabbix_delete_proxies does on Zabbix MCP Server

AI agents call zabbix_delete_proxies 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_proxies needs a policy

Deleting proxies is an irreversible operation that removes infrastructure management components from the Zabbix monitoring system. This cannot be undone without reconfiguration and could disrupt monitoring for distributed systems relying on those proxies. This falls squarely into the Destructive category as it permanently removes data/configuration rather than just modifying it.

From the tool's definition Tool name contains 'delete' and description states 'Delete proxies from Zabbix', which irreversibly removes proxy infrastructure configuration.

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

How to control zabbix_delete_proxies

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

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

zabbix_delete_proxies 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_proxies

What does the zabbix_delete_proxies tool do? +

Delete proxies 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_proxies? +

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

zabbix_delete_proxies 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_proxies? +

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

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

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