Link templates to a host in Zabbix
AI agents use zabbix_link_templates_to_host 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.
Linking templates to a host modifies the host's monitoring configuration by applying template items, triggers, and rules to that host. While reversible (unlike deletion), this is a Write operation that affects infrastructure state and monitoring behavior. The severity is high because unauthorized template linking could enable monitoring bypass, deploy malicious checks, or alter alerting rules for critical systems.
From the tool's definition Tool performs 'Link templates to a host' — this creates associations between templates and hosts in Zabbix, modifying the host's configuration and applied monitoring rules. This is a reversible configuration change (templates can be unlinked).
Documented attack patterns abuse exactly the kind of access zabbix_link_templates_to_host 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_link_templates_to_host:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_link_templates_to_host": {
"limits": [
{
"counter": "zabbix_link_templates_to_host_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zabbix_link_templates_to_host 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.
Link templates to a host 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_link_templates_to_host: 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_link_templates_to_host 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_link_templates_to_host 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_link_templates_to_host. 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_link_templates_to_host 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.