Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

regexp_get

Read-only

Retrieve reusable global regular expressions from Zabbix for LLD rules and trigger expressions; filter by name or ID, and include test expressions when needed.

Instructions

Retrieve global regular expressions. These named regexp objects are reusable across Zabbix -- referenced in LLD (Low-Level Discovery) rules to filter discovered entities, in trigger expressions, and elsewhere. Each regexp can contain multiple test expressions with different match types (character string included, result is TRUE/FALSE, etc.). Use selectExpressions to include the test expressions.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return 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: name, regexpid, test_string. Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the regexp 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: regexpid, name. Properties: description (8.0+), name, regexpid, test_string.
`search`	No	Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description (8.0+), name, test_string.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`raw_json`	No	Strips 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.
`regexpids`	No	Return only regular expressions with the given IDs.
`sortfield`	No	Sort by one or more of: regexpid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`countOutput`	No	Return the count of matching results instead of the actual data.
`searchByAny`	No	If true, return results matching ANY search field (OR). Default is ALL fields (AND).
`extra_params`	No	Other native regexp.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectExpressions. 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.
`searchWildcardsEnabled`	No	If true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.41.0Oct 20, 2026

TDQS

B3.2/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 useful domain context (reusable objects, multiple test expressions with different match types) but says nothing about return shape, pagination, or the raw_json/prompt-injection tradeoff that lives only in 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?

Purpose is front-loaded in the first sentence and the whole thing is four sentences. The parenthetical about match types (character string included, result is TRUE/FALSE, etc.) is somewhat expendable, keeping it from a 5.

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 and full 100% parameter coverage, the description need not explain return values. It adequately frames the resource and its Zabbix role, leaving only return/pagination behavior unspecified, which the output schema covers.

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% (all 13 params documented, including the nuanced raw_json and extra_params), so the schema carries the load and baseline 3 applies. The description only adds the hint that selectExpressions pulls in test expressions, which is marginal beyond what the schema already states.

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?

States a specific verb (Retrieve) and resource (global regular expressions), and goes further by explaining what these named objects are and where they are referenced (LLD rules, trigger expressions). An agent can identify the resource clearly, though it does not explicitly contrast itself with sibling *_get tools.

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?

The description explains the domain role of regexp objects but gives no when-to-use guidance, no exclusions, and no alternative tools to prefer. An agent gets no routing signal for this tool versus the many other *_get tools or zabbix_raw_api_call.

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

Deploy Server