Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zia_list_cloud_app_ssl_policy

Read-only

Get the ZIA cloud-application catalog for SSL Inspection rules. Use search or category filters to find canonical enum strings (e.g., ONEDRIVE) for creating or updating rules.

Instructions

List the ZIA cloud-application catalog scoped to SSL Inspection rules — returns the canonical enum strings the SSL Inspection API will accept in the cloud_applications field (e.g. ONEDRIVE, SHAREPOINT_ONLINE). Use this to resolve enum names before creating or updating SSL Inspection rules. Supports server-side filtering (search, app_class, group_results) and JMESPath via the query parameter. Pass app_class to narrow the catalog by category when the user describes a kind of app — valid values: SOCIAL_NETWORKING, STREAMING_MEDIA, WEBMAIL, INSTANT_MESSAGING, BUSINESS_PRODUCTIVITY, ENTERPRISE_COLLABORATION, SALES_AND_MARKETING, SYSTEM_AND_DEVELOPMENT, CONSUMER, HOSTING_PROVIDER, IT_SERVICES, FILE_SHARE, DNS_OVER_HTTPS, HUMAN_RESOURCES, LEGAL, HEALTH_CARE, FINANCE, CUSTOM_CAPP, AI_ML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoServer-side substring filter on application name (e.g. 'sharepoint', 'onedrive'). Use this first to narrow results before applying a JMESPath query.
app_classNoFilter the cloud-application catalog by category (``app_class``). Use this when the user describes a kind of application — e.g. 'webmail', 'AI tools', 'file sharing', 'streaming' — rather than a specific app. Must be one of the canonical ZIA enum values: ``SOCIAL_NETWORKING``, ``STREAMING_MEDIA``, ``WEBMAIL``, ``INSTANT_MESSAGING``, ``BUSINESS_PRODUCTIVITY``, ``ENTERPRISE_COLLABORATION``, ``SALES_AND_MARKETING``, ``SYSTEM_AND_DEVELOPMENT``, ``CONSUMER``, ``HOSTING_PROVIDER``, ``IT_SERVICES``, ``FILE_SHARE``, ``DNS_OVER_HTTPS``, ``HUMAN_RESOURCES``, ``LEGAL``, ``HEALTH_CARE``, ``FINANCE``, ``CUSTOM_CAPP``, ``AI_ML``. The full live list is whatever ``client.zia.cloudappcontrol.get_rule_type_mapping()`` returns.
pageNoPage offset for pagination.
page_sizeNoPage size (default 200, maximum 1000).
group_resultsNoIf true, return application counts grouped by category.
queryNoJMESPath expression for client-side filtering/projection. Example: '[?contains(name, `Share`)].{id: id, name: name}'.
serviceNoThe service to use.zia

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations declare readOnlyHint=true, and the description consistently indicates a read operation (list). The description adds behavioral context such as the scope (SSL Inspection) and output (canonical enum strings), but does not disclose additional details like rate limits or pagination behavior beyond what parameters imply.

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?

The description is a single, well-structured paragraph that front-loads the purpose, includes examples and parameter details, and uses concise language. It is informative without being overly verbose.

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?

Given the tool has 7 optional parameters, annotations, and an output schema, the description provides sufficient context: purpose, usage, filtering capabilities, and parameter guidance (including enum values). It does not need to explain the output schema since it exists separately.

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 descriptions cover all 7 parameters (100% coverage), so baseline is 3. However, the description adds value by listing the valid enum values for app_class (e.g., SOCIAL_NETWORKING, AI_ML) and summarizing filtering options, which is not present in the schema description for app_class (which only says 'Must be one of the canonical ZIA enum values').

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 lists the ZIA cloud-application catalog scoped to SSL Inspection rules and returns canonical enum strings accepted by the SSL Inspection API. This is a specific verb+resource and distinguishes it from sibling list tools like zia_list_cloud_app_policy.

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?

The description explicitly advises using this tool to resolve enum names before creating or updating SSL Inspection rules, providing a clear use case. It also mentions supported filtering options, though it does not explicitly contrast with alternative tools.

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