AI agents call zabbix_api_list to retrieve information from Zabbix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern (ending in '_list') and server context indicate this is a data retrieval tool with no side effects. However, since the description is empty, there is inherent uncertainty about potential undocumented capabilities. Zabbix API list operations typically query monitoring data (hosts, items, triggers, etc.), which falls under Read category.
From the tool's definition Tool name 'zabbix_api_list' suggests a listing/query operation. Server description mentions '40+ tools for hosts, items, triggers, templates, problems' and 'read-only mode', indicating this tool retrieves data. Empty description limits confidence.
Documented attack patterns abuse exactly the kind of access zabbix_api_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zabbix, and nothing reaches the server without passing your rules. This is the rule we recommend for zabbix_api_list:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_api_list": {}
}
}zabbix_api_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
zabbix_api_list. It is categorised as a Read tool in the Zabbix MCP Server, which means it retrieves data without modifying state.
Register the Zabbix MCP server in PolicyLayer and add a rule for zabbix_api_list: 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. Nothing to install.
zabbix_api_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zabbix_api_list 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_api_list. 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_api_list is provided by the Zabbix MCP server (mpeirone/zabbix-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zabbix, 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.
3 Zabbix tools catalogued and risk-classified — across an index of 43,000+ MCP servers.