Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zia_list_cloud_app_policy

Read-only

Retrieve canonical cloud-application enum strings (e.g., ONEDRIVE, SHAREPOINT_ONLINE) for ZIA policy rules. Filter by search term or category, with pagination and JMESPath support.

Instructions

List the ZIA policy-engine cloud-application catalog — canonical enum strings (e.g. ONEDRIVE, ONEDRIVE_PERSONAL, SHAREPOINT_ONLINE) consumed by Web DLP, Cloud App Control, File Type Control, Bandwidth Classes, and Advanced Settings. Use this when you need the exact enum to pass into a policy rule's cloud_applications field. 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 instead of a specific one — 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. Examples: '[?contains(name, `Share`)].{id: id, name: name}', '[?app_class==`ENTERPRISE_COLLABORATION`].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 already declare readOnlyHint=true, so the description adds value by explaining filtering capabilities and example values, but does not detail pagination behavior or response structure. The description is adequate but not especially rich beyond the annotations.

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?

The description is three concise sentences, front-loaded with the primary purpose, then usage context and parameter guidance. Every sentence adds value with no redundancy.

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 parameters (0 required), output schema exists, and sibling tools are numerous, the description covers the core purpose and key usage scenarios. It could briefly mention pagination parameters, but the schema already covers them, so completeness is high.

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%, baseline 3. The description adds semantic guidance by explaining the role of filtering parameters and listing valid app_class values, which goes beyond the schema's 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 verb ('List') and the resource ('ZIA policy-engine cloud-application catalog'), and distinguishes it from sibling tools by specifying the domain (ZIA policy engine) and the use case (canonical enum strings for policy rules).

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 states when to use the tool ('when you need the exact enum to pass into a policy rule's cloud_applications field') and provides guidance on using the app_class parameter for categorizing apps. However, it does not explicitly disclaim when not to use it or compare with sibling 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