Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

authentication_get

Read-only

Retrieves server-wide Zabbix authentication settings—internal, LDAP, SAML, HTTP, password complexity, login limits, and MFA—to audit or verify configuration.

Instructions

Get the global authentication settings. Returns the server-wide configuration for authentication methods: internal auth, LDAP defaults, SAML settings, HTTP authentication, password complexity requirements, login attempt limits, and MFA enforcement. This is a singleton object -- there are no IDs to filter by.

Input Schema

NameRequiredDescriptionDefault
outputNoProperties of the authentication object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: authentication_type, disabled_usrgrpid (6.4+), http_auth_enabled, http_case_sensitive, http_login_form, http_strip_domains, jit_provision_interval (6.4+), ldap_auth_enabled (6.4+), ldap_base_dn (removed in 6.2), ldap_bind_dn (removed in 6.2), ldap_bind_password (removed in 6.2), ldap_case_sensitive, ldap_configured (removed in 6.4), ldap_host (removed in 6.2), ldap_jit_status (6.4+), ldap_port (removed in 6.2), ldap_search_attribute (removed in 6.2), ldap_userdirectoryid (6.2+), mfa_status (7.0+), mfaid (7.0+), passwd_check_rules (6.0+), passwd_min_length (6.0+), saml_auth_enabled, saml_case_sensitive, saml_encrypt_assertions (removed in 6.4), saml_encrypt_nameid (removed in 6.4), saml_idp_entityid (removed in 6.4), saml_jit_status (6.4+), saml_nameid_format (removed in 6.4), saml_sign_assertions (removed in 6.4), saml_sign_authn_requests (removed in 6.4), saml_sign_logout_requests (removed in 6.4), saml_sign_logout_responses (removed in 6.4), saml_sign_messages (removed in 6.4), saml_slo_url (removed in 6.4), saml_sp_entityid (removed in 6.4), saml_sso_url (removed in 6.4), saml_username_attribute (removed in 6.4).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
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.
extra_paramsNoOther native authentication.get parameters, merged into the request as-is. authentication.get has no parameters beyond the typed ones. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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: +[
      +  {
      +    "additionalProperties": false,
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "authentication_type",
      +        "disabled_usrgrpid",
      +        "http_auth_enabled",
      +        "http_case_sensitive",
      +        "http_login_form",
      +        "http_strip_domains",
      +        "jit_provision_interval",
      +        "ldap_auth_enabled",
      +        "ldap_base_dn",
      +        "ldap_bind_dn",
      +        "ldap_bind_password",
      +        "ldap_case_sensitive",
      +        "ldap_configured",
      +        "ldap_host",
      +        "ldap_jit_status",
      +        "ldap_port",
      +        "ldap_search_attribute",
      +        "ldap_userdirectoryid",
      +        "mfa_status",
      +        "mfaid",
      +        "passwd_check_rules",
      +        "passwd_min_length",
      +        "saml_auth_enabled",
      +        "saml_case_sensitive",
      +        "saml_encrypt_assertions",
      +        "saml_encrypt_nameid",
      +        "saml_idp_entityid",
      +        "saml_jit_status",
      +        "saml_nameid_format",
      +        "saml_sign_assertions",
      +        "saml_sign_authn_requests",
      +        "saml_sign_logout_requests",
      +        "saml_sign_logout_responses",
      +        "saml_sign_messages",
      +        "saml_slo_url",
      +        "saml_sp_entityid",
      +        "saml_sso_url",
      +        "saml_username_attribute"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the authentication 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: 'extend'. Properties: authentication_type, disabled_usrgrpid (6.4+), http_auth_enabled, http_case_sensitive, http_login_form, http_strip_domains, jit_provision_interval (6.4+), ldap_auth_enabled (6.4+), ldap_base_dn (removed in 6.2), ldap_bind_dn (removed in 6.2), ldap_bind_password (removed in 6.2), ldap_case_sensitive, ldap_configured (removed in 6.4), ldap_host (removed in 6.2), ldap_jit_status (6.4+), ldap_port (removed in 6.2), ldap_search_attribute (removed in 6.2), ldap_userdirectoryid (6.2+), mfa_status (7.0+), mfaid (7.0+), passwd_check_rules (6.0+), passwd_min_length (6.0+), saml_auth_enabled, saml_case_sensitive, saml_encrypt_assertions (removed in 6.4), saml_encrypt_nameid (removed in 6.4), saml_idp_entityid (removed in 6.4), saml_jit_status (6.4+), saml_nameid_format (removed in 6.4), saml_sign_assertions (removed in 6.4), saml_sign_authn_requests (removed in 6.4), saml_sign_logout_requests (removed in 6.4), saml_sign_logout_responses (removed in 6.4), saml_sign_messages (removed in 6.4), saml_slo_url (removed in 6.4), saml_sp_entityid (removed in 6.4), saml_sso_url (removed in 6.4), saml_username_attribute (removed in 6.4)."New value: +"Properties of the authentication object to return. Pass 'extend' for all, or a list of property names. Default when omitted: 'extend'. Properties: authentication_type, disabled_usrgrpid (6.4+), http_auth_enabled, http_case_sensitive, http_login_form, http_strip_domains, jit_provision_interval (6.4+), ldap_auth_enabled (6.4+), ldap_base_dn (removed in 6.2), ldap_bind_dn (removed in 6.2), ldap_bind_password (removed in 6.2), ldap_case_sensitive, ldap_configured (removed in 6.4), ldap_host (removed in 6.2), ldap_jit_status (6.4+), ldap_port (removed in 6.2), ldap_search_attribute (removed in 6.2), ldap_userdirectoryid (6.2+), mfa_status (7.0+), mfaid (7.0+), passwd_check_rules (6.0+), passwd_min_length (6.0+), saml_auth_enabled, saml_case_sensitive, saml_encrypt_assertions (removed in 6.4), saml_encrypt_nameid (removed in 6.4), saml_idp_entityid (removed in 6.4), saml_jit_status (6.4+), saml_nameid_format (removed in 6.4), saml_sign_assertions (removed in 6.4), saml_sign_authn_requests (removed in 6.4), saml_sign_logout_requests (removed in 6.4), saml_sign_logout_responses (removed in 6.4), saml_sign_messages (removed in 6.4), saml_slo_url (removed in 6.4), saml_sp_entityid (removed in 6.4), saml_sso_url (removed in 6.4), saml_username_attribute (removed in 6.4)."
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "authentication_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

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=false, so safety is covered. The description adds the singleton nature and the breadth of returned settings, but omits notable behavioral traits such as the security-disclaimer preamble that wraps the response (and the raw_json bypass policy), which materially affect how an agent consumes the result.

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

Conciseness5/5

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

Three tight sentences: purpose first, returned content second, singleton constraint last. No filler and nothing repeated from the schema.

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?

For a zero-required-parameter singleton read with no output schema, the description supplies the essential missing piece by enumerating what comes back. It would be fully complete if it flagged the prompt-injection disclaimer wrapper on the response, which an agent needs to interpret the payload correctly.

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% and every parameter (output, server, raw_json, extra_params) is thoroughly documented in the schema itself, including per-release availability notes. The description adds only the 'no IDs to filter by' hint, so the schema is doing essentially all the work; baseline 3 applies.

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 opens with a specific verb and resource ('Get the global authentication settings') and enumerates the concrete configuration domains returned (LDAP defaults, SAML, HTTP auth, password complexity, MFA enforcement). It implicitly separates itself from siblings like user_checkauthentication or mfa_get by stressing 'server-wide' and 'singleton', though it never names an alternative explicitly.

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 only usage guidance is 'This is a singleton object -- there are no IDs to filter by', which usefully implies you call it with no scoping arguments. There is no statement of when to prefer this over user_checkauthentication (per-user auth test) or settings_get (broader system settings), so routing must be inferred from the tool name.

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