Acknowledges one or more events/problems in Zabbix.
AI agents use zabbix_acknowledge_event to create or update resources in Zabbix MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zabbix MCP Server environment.
Acknowledging an event modifies the state of monitoring data in Zabbix—specifically marking events or problems as acknowledged. This is a reversible operation (acknowledgment can typically be undone) and does not delete data or execute arbitrary code. It fits the Write category as it creates or modifies data reversibly.
From the tool's definition Tool name 'zabbix_acknowledge_event' and description 'Acknowledges one or more events/problems in Zabbix' indicate modification of event/problem state through an acknowledge action, which changes data (event acknowledgment status) reversibly.
Documented attack patterns abuse exactly the kind of access zabbix_acknowledge_event 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_acknowledge_event:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_acknowledge_event": {
"limits": [
{
"counter": "zabbix_acknowledge_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zabbix_acknowledge_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Acknowledges one or more events/problems in Zabbix. It is categorised as a Write tool in the Zabbix MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_acknowledge_event: 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_acknowledge_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zabbix_acknowledge_event 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_acknowledge_event. 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_acknowledge_event 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.