현재 활성화된 Zabbix 트리거(Triggers) 목록을 조회합니다.
AI agents call list_triggers 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 retrieves and displays information about active triggers in Zabbix infrastructure. It performs a read-only query operation analogous to 'list' or 'get', returning current state data without modifying, executing, or deleting anything. The blast radius of misuse is minimal — an agent could retrieve unwanted trigger information but cannot alter system state, execute commands, or cause destructive changes.
From the tool's definition Tool name 'list_triggers' and description indicating it 'lists/queries current active Zabbix triggers' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
현재 활성화된 Zabbix 트리거(Triggers) 목록을 조회합니다. 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 list_triggers: 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.
list_triggers 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 list_triggers 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 list_triggers. 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.
list_triggers is provided by the Zabbix MCP Server MCP server (mchlkim/zabbix-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →