Authenticate with Zabbix server and obtain session token. Required before using other tools.
AI agents call zabbix_login as a supporting operation in Zabbix MCP Server workflows.
This tool performs authentication and session establishment rather than reading, writing, executing, or destroying data. It obtains a session token that enables subsequent API calls. While not destructive or financial, misuse (e.g., credential theft or session hijacking) carries medium severity since the resulting token grants access to a broad monitoring infrastructure with 90+ tools.
From the tool's definition Authenticate with Zabbix server and obtain session token. Required before using other tools.
Documented attack patterns abuse exactly the kind of access zabbix_login 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_login:
{
"version": "1",
"default": "deny",
"tools": {
"zabbix_login": {
"limits": [
{
"counter": "zabbix_login_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} zabbix_login gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Authenticate with Zabbix server and obtain session token. Required before using other tools. It is categorised as a Other tool in the Zabbix MCP Server MCP Server, which means it performs auxiliary operations.
Register the Zabbix MCP Server MCP server in PolicyLayer and add a rule for zabbix_login: 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_login is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zabbix_login 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_login. 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_login 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.