Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zia_get_mobile_advanced_settings

Read-only

Retrieve mobile advanced threat settings for ZIA, including 8 boolean controls for blocking malicious apps, vulnerable apps, data exfiltration, and unknown server communication. Use this read-only call before updating to merge changes.

Instructions

Get the ZIA Mobile Advanced Threat Settings block (read-only) — the tenant-wide singleton that governs the Mobile Malware Protection policy applied to traffic from mobile clients (iOS / Android via the Zscaler Client Connector). Returns 8 boolean knobs: block_apps_with_malicious_activity, block_apps_with_known_vulnerabilities, block_apps_sending_unencrypted_user_credentials, block_apps_sending_location_info, block_apps_sending_personally_identifiable_info, block_apps_sending_device_identifier, block_apps_communicating_with_ad_websites, block_apps_communicating_with_remote_unknown_servers. Always call this before zia_update_mobile_advanced_settings so partial updates can be merged onto the existing payload (the update is PUT-replace). Supports JMESPath client-side filtering via the query parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoJMESPath expression for client-side filtering/projection of the returned settings dict (e.g. "{malicious: block_apps_with_malicious_activity, vuln: block_apps_with_known_vulnerabilities}").
serviceNoThe service to use.zia
Behavior5/5

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

Annotations provide readOnlyHint=true, and the description confirms read-only access. It adds detail about the singleton nature, the specific boolean fields, and the PUT-replace behavior of the update sister tool, going beyond what annotations offer.

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?

Description is concise: two sentences for purpose, usage guidance, and field listing. Front-loaded with key info. Slight redundancy on field listing but overall effective.

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?

No output schema exists, but the description lists all 8 boolean knobs, explains the singleton nature, and provides usage context with the update tool. This is complete for a read-only get tool.

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 the baseline is 3. The description mentions JMESPath filtering and the service parameter default, but adds limited extra meaning beyond the schema descriptions.

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?

The description clearly states the tool retrieves the ZIA Mobile Advanced Threat Settings block, a tenant-wide singleton for mobile malware protection policy. It specifies the 8 boolean knobs returned. This distinguishes it from siblings like zia_get_advanced_settings and other 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 Guidelines4/5

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

Explicitly instructs to call this tool before zia_update_mobile_advanced_settings for merging partial updates, indicating usage order. The JMESPath filtering capability is mentioned. Lacks explicit exclusion of alternatives but provides strong usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zscaler/zscaler-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server