Retrieve monitoring items from Zabbix. Use this to see what metrics are being collected.
AI agents call zabbix_get_items to retrieve information from Zabbix MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing monitoring configuration data without creating, modifying, deleting, or executing any operations. It has minimal security impact as it only exposes information about what metrics are already being monitored. Misuse would result in information disclosure rather than system compromise.
From the tool's definition Tool name is 'zabbix_get_items' and description states 'Retrieve monitoring items from Zabbix. Use this to see what metrics are being collected.' The verbs 'retrieve' and 'see' indicate read-only data retrieval with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access zabbix_get_items 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_get_items:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_get_items": {}
}
} zabbix_get_items 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.
Retrieve monitoring items from Zabbix. Use this to see what metrics are being collected. It is categorised as a Read tool in the Zabbix MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_get_items: 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_get_items 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_get_items 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_get_items. 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_get_items 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.