Skip to main content
Glama
initMAX

Zabbix MCP Server

proxy_get

Read-only

Retrieve Zabbix proxy configurations to monitor distributed data collection. Filter by host assignment, mode, or connection settings, and optionally include assigned hosts.

Instructions

Retrieve Zabbix proxies. Proxies collect monitoring data on behalf of the Zabbix server, enabling distributed monitoring across network segments, firewalls, and geographic regions. Each proxy has a mode (0=active, 1=passive), connection settings, and a list of assigned hosts. Use selectHosts to include assigned hosts, selectInterface for connection details. Filter with with_hosts to find proxies that are actively monitoring hosts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: address (7.0+), allowed_addresses (7.0+), auto_compress (removed in 7.0), compatibility (6.4+), custom_timeouts (7.0+), host (removed in 7.0), lastaccess, local_address (7.0+), local_port (7.0+), name (7.0+), operating_mode (7.0+), port (7.0+), proxy_address (removed in 7.0), proxy_groupid (7.0+), state (7.0+), status (removed in 7.0), timeout_browser (7.0+), timeout_db_monitor (7.0+), timeout_external_check (7.0+), timeout_http_agent (7.0+), timeout_script (7.0+), timeout_simple_check (7.0+), timeout_snmp_agent (7.0+), timeout_ssh_agent (7.0+), timeout_telemetry_query (8.0+), timeout_telnet_agent (7.0+), timeout_zabbix_agent (7.0+), tls_accept, tls_connect, tls_issuer, tls_subject, version (6.4+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the proxy object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: proxyid, name, operating_mode, state. Properties: address (7.0+), allowed_addresses (7.0+), auto_compress (removed in 7.0), compatibility (6.4+), custom_timeouts (7.0+), description, host (removed in 7.0), lastaccess, local_address (7.0+), local_port (7.0+), name (7.0+), operating_mode (7.0+), port (7.0+), proxy_address (removed in 7.0), proxy_groupid (7.0+), proxyid, state (7.0+), status (removed in 7.0), timeout_browser (7.0+), timeout_db_monitor (7.0+), timeout_external_check (7.0+), timeout_http_agent (7.0+), timeout_script (7.0+), timeout_simple_check (7.0+), timeout_snmp_agent (7.0+), timeout_ssh_agent (7.0+), timeout_telemetry_query (8.0+), timeout_telnet_agent (7.0+), timeout_zabbix_agent (7.0+), tls_accept, tls_connect, tls_issuer, tls_subject, version (6.4+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: address (7.0+), allowed_addresses (7.0+), description, host (removed in 7.0), local_address (7.0+), local_port (7.0+), name (7.0+), port (7.0+), proxy_address (removed in 7.0), timeout_browser (7.0+), timeout_db_monitor (7.0+), timeout_external_check (7.0+), timeout_http_agent (7.0+), timeout_script (7.0+), timeout_simple_check (7.0+), timeout_snmp_agent (7.0+), timeout_ssh_agent (7.0+), timeout_telemetry_query (8.0+), timeout_telnet_agent (7.0+), timeout_zabbix_agent (7.0+), tls_issuer, tls_subject.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
proxyidsNoReturn only proxies with the given IDs.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
sortfieldNoSort by one or more of: proxyid (7.0+), name (7.0+), operating_mode (7.0+), host (removed in 7.0), hostid (removed in 7.0), status (removed in 7.0) (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
with_hostsNoReturn only proxies that have at least one host assigned to them.
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
extra_paramsNoOther native proxy.get parameters, merged into the request as-is. Parameters: proxy_groupids (7.0+). Sub-object selects (value 'extend', 'count' or a list of property names): selectApm (8.0+), selectAssignedHosts (7.0+), selectHosts, selectInterface (removed in 7.0), selectProxyGroup (7.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds domain semantics (mode 0=active/1=passive, proxies sit across network segments) but says nothing about pagination, result limits, or the security-wrapped response that the raw_json parameter hints at.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the verb and resource, and the explanatory material about proxy purpose is short and relevant. Slightly more prose than strictly needed for a read tool whose schema already does the heavy lifting, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and all 14 optional parameters are fully documented in the schema. The description supplies enough domain framing (modes, distributed monitoring) for an agent to call the tool correctly, though it does not mention the raw_json policy implications that matter for LLM clients.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented in the schema; baseline is 3. The description mentions only three of fourteen parameters (selectHosts, selectInterface, with_hosts) and notably omits the version caveat that selectInterface was removed in 7.0, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Retrieve Zabbix proxies') and immediately defines what a proxy is ('collect monitoring data on behalf of the Zabbix server'), which implicitly distinguishes it from the sibling proxygroup_get. An agent can identify the resource and its scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives per-parameter usage hints ('Use selectHosts to include assigned hosts', 'Filter with with_hosts') but never states when to choose this tool over alternatives such as proxygroup_get, nor any exclusions or prerequisites. Usage is implied rather than framed as when/when-not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.