AI agents use zabbix_create_trigger 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.
This tool creates new monitoring triggers, which is a reversible write operation on Zabbix infrastructure configuration. While triggers can indirectly affect alerting behavior and operations, the action itself is write-level (not destructive, as triggers can be deleted/modified).
From the tool's definition Tool name 'zabbix_create_trigger' and description 'Create a new trigger in Zabbix' indicate data creation/modification. Triggers are monitoring rules that detect conditions and generate alerts—creating them modifies the monitoring configuration reversibly.
Documented attack patterns abuse exactly the kind of access zabbix_create_trigger 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_create_trigger:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_create_trigger": {
"limits": [
{
"counter": "zabbix_create_trigger_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zabbix_create_trigger 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.
Create a new trigger 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_create_trigger: 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_create_trigger 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_create_trigger 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_create_trigger. 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_create_trigger 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.