Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

role_get

Read-only

Retrieve Zabbix user roles and their RBAC permissions, including visible UI sections, allowed API methods, and permitted actions, with optional rule details.

Instructions

Retrieve user roles. Roles define what a user can do in Zabbix via granular RBAC rules: which UI sections are visible, which API methods are allowed, and what actions (acknowledge, close, suppress) are permitted. Built-in roles: Super admin (type=3), Admin (type=2), User (type=1), Guest (type=4). Use selectRules to include the full permission rule set for each role.

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, readonly, roleid, type. Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the role 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: roleid, name, type. Properties: name, readonly, roleid, type.
`search`	No	Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`roleids`	No	Return only roles with the given IDs.
`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.
`sortfield`	No	Sort by one or more of: roleid, 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 role.get parameters, merged into the request as-is. Parameters: current (8.0+). Sub-object selects (value 'extend', 'count' or a list of property names): selectRules, selectUsers. 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

A3.6/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 and the bar is lower. The description adds domain semantics about what roles govern but says nothing about pagination, return format, or auth requirements beyond the annotation scope.

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?

Front-loaded with the purpose, then useful context, then the built-in role table, then a single actionable tip. Four sentences with little waste, though the RBAC explainer is somewhat longer than strictly needed for tool selection.

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 all 13 parameters documented in the schema, the description only needs to supply domain context — which it does via the RBAC explanation and role type mapping. Nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning by enumerating the built-in role type values (Super admin=3, Admin=2, User=1, Guest=4) that the 'type' filter key expects, plus flagging selectRules for the permission rule set.

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 clear verb+resource ('Retrieve user roles') and goes further by defining what a role is in Zabbix (RBAC: UI sections, API methods, actions). It never distinguishes itself from near siblings like user_get or usergroup_get, so it falls short of a 5.

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?

Usage is only implied — it is the read tool for roles and one parameter directive is given ('Use selectRules to include the full permission rule set'). There is no explicit when-to-use, when-not, or alternative routing guidance.

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

Deploy Server