Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

drule_get

Read-only

Retrieve network discovery rules to inspect IP ranges and checks used for automatic host discovery in Zabbix, with filtering, sorting, and count options.

Instructions

Retrieve network discovery rules. Network discovery rules define IP ranges and checks (SNMP, agent, ICMP, etc.) used to automatically find new hosts on the network. Discovered hosts and services are stored as dhost/dservice objects.

Input 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: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the drule object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: druleid, name, status. Properties: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: delay, error (7.0+), iprange, name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
druleidsNoReturn only network discovery rules 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: druleid, name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
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 drule.get parameters, merged into the request as-is. Parameters: dhostids, dserviceids, groupCount, limitSelects. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDChecks, selectDHosts. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "dhostids",
      +        "dserviceids",
      +        "groupCount",
      +        "limitSelects",
      +        "selectDChecks",
      +        "selectDHosts"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native drule.get parameters, merged into the request as-is. Parameters: dhostids, dserviceids, limitSelects. Sub-object selects (value 'extend', 'count' or a list of property names): selectDChecks, selectDHosts. 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."New value: +"Other native drule.get parameters, merged into the request as-is. Parameters: dhostids, dserviceids, groupCount, limitSelects. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDChecks, selectDHosts. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "concurrency_max",
      +        "delay",
      +        "druleid",
      +        "error",
      +        "iprange",
      +        "name",
      +        "nextcheck",
      +        "proxy_hostid",
      +        "proxyid",
      +        "status"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "concurrency_max",
      +        "delay",
      +        "druleid",
      +        "error",
      +        "iprange",
      +        "name",
      +        "nextcheck",
      +        "proxy_hostid",
      +        "proxyid",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the drule 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: druleid, name, status. Properties: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status."New value: +"Properties of the drule object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: druleid, name, status. Properties: concurrency_max (7.0+), delay, druleid, error (7.0+), iprange, name, nextcheck (removed in 6.4), proxy_hostid (removed in 7.0), proxyid (7.0+), status."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "delay",
      +        "error",
      +        "iprange",
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "druleid",
      +      "name"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "druleid",
      +        "name"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: druleid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: druleid, name (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "drule_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds useful domain context, notably that discovered hosts and services land as dhost/dservice objects, but says nothing about result volume, pagination via limit, count modes, or the security-wrapped response — all of which the agent only finds by reading the schema.

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?

Three short sentences with the core action front-loaded and no filler. The closing sentence about dhost/dservice storage is mildly tangential to retrieval but still useful orientation for a discovery rule's downstream effects.

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

Completeness5/5

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

For a 13-parameter tool the description is intentionally thin, but every parameter, default, and output mode is documented in the schema with exception detail, and the annotations cover the read-only profile. Nothing an agent needs in order to invoke it correctly is missing from the combined definition.

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 description coverage is 100%, including the elaborate raw_json and extra_params documentation, so parameter meaning is fully carried by structured fields. The description contributes nothing parameter-specific, which is the expected baseline when the schema does the heavy lifting.

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

Purpose4/5

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

The description uses a specific verb and resource ('Retrieve network discovery rules') and then defines what a discovery rule is — IP ranges plus checks (SNMP, agent, ICMP) — which lets an agent distinguish this from dcheck_get or dhost_get. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully self-differentiating.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, no prerequisite information (permissions, server targeting), and no mention of the sibling tools that retrieve related discovery data. The description only says what the resource is, leaving the agent to infer the invocation context.

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