zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zia_list_cloud_app_policy

Read-only

List the ZIA policy-engine cloud-application catalog (Cloud App Control).

Instructions

List the ZIA policy-engine cloud-application catalog (Cloud App Control).

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`query`	No	Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response.
`search`	No
`app_class`	No
`page_size`	No
`group_results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.15.3Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / app_class / title
```
Added value: +"App Class"
```
addedInput schema / properties / group_results / title
```
Added value: +"Group Results"
```
addedInput schema / properties / page / title
```
Added value: +"Page"
```
addedInput schema / properties / page_size / title
```
Added value: +"Page Size"
```

changedInput schema / properties / query / description

Previous value: -"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response."

addedInput schema / properties / query / title
```
Added value: +"Query"
```
addedInput schema / properties / search / title
```
Added value: +"Search"
```

addedInput schema / title

Added value: +"zia_list_cloud_app_policyArguments"

Changed16 schema fields changedv0.14.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / app_class / description

Removed value: -"Filter 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."

removedInput schema / properties / app_class / title
```
Removed value: -"App Class"
```

removedInput schema / properties / group_results / description

Removed value: -"If true, return application counts grouped by category."

removedInput schema / properties / group_results / title
```
Removed value: -"Group Results"
```
removedInput schema / properties / page / description
```
Removed value: -"Page offset for pagination."
```
removedInput schema / properties / page / title
```
Removed value: -"Page"
```

removedInput schema / properties / page_size / description

Removed value: -"Page size (default 200, maximum 1000)."

removedInput schema / properties / page_size / title
```
Removed value: -"Page Size"
```

changedInput schema / properties / query / description

Previous value: -"JMESPath expression for client-side filtering/projection. Examples: '[?contains(name, `Share`)].{id: id, name: name}', '[?app_class==`ENTERPRISE_COLLABORATION`].name'."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

removedInput schema / properties / search / description

Removed value: -"Server-side substring filter on application name (e.g. 'sharepoint', 'onedrive'). Use this first to narrow results before applying a JMESPath query."

removedInput schema / properties / search / title
```
Removed value: -"Search"
```

removedInput schema / properties / service

Removed value: -{
-  "default": "zia",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}

removedInput schema / title

Removed value: -"zia_list_cloud_app_policyArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zia_list_cloud_app_policyOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description doesn't add behavioral details like pagination defaults, whether group_results changes response shape, or what app_class filtering does beyond the parameter name. With readOnlyHint already provided, a 3 is appropriate – the description adds the scope ('policy-engine catalog') but lacks deeper behavioral context like response format or limit behavior.

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 main description is a single concise sentence that efficiently conveys purpose. The schema description for 'query' is verbose but earns its place with actionable warnings and usage examples. No fluff or redundancy. The tool description itself is minimal, and the param description is rich without being bloated.

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 6 optional parameters and no output schema, the description leaves a lot unexplained (pagination behavior, what group_results does, app_class allowed values). However, the excellent query param documentation compensates for some gaps, and readOnlyHint covers the safety profile. Schema coverage is low at 17%, but the query param semantics are so well documented that the overall tool is reasonably complete for an experienced agent. Still, the 5 other params lack any description, so it's not a 5.

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?

Only the 'query' parameter has an in-schema description (17% coverage), but that description is exceptionally detailed and provides critical semantics: JMESPath usage, field-name casing warnings, and a concrete tip to call without query first. The remaining 5 parameters (page, search, app_class, page_size, group_results) are undocumented, and the description adds no extra meaning for them. However, the query parameter alone carries significant value, pushing this above baseline. For the undocumented params, the description should have provided more guidance, but the query doc is a strong asset.

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 'List the ZIA policy-engine cloud-application catalog (Cloud App Control)' clearly identifies the resource (cloud-application catalog) and action (list), and the parenthetical 'Cloud App Control' provides domain context. It distinguishes from siblings that list rules (e.g., zia_list_cloud_app_control_rules) or actions (zia_list_cloud_app_control_actions). A minor gap: it's not explicit about whether this returns the full catalog vs. pageable subset, but the verb+resource is clear.

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 description mentions it's a catalog listing, which implies it's for browsing available cloud apps before creating policy rules, but it doesn't explicitly state when to use this vs. sibling tools like zia_list_cloud_app_control_rules or zia_get_cloud_app_control_rule. The purpose is clear enough to infer usage, but there's no explicit when/when-not guidance. The schema's detailed query parameter hints at filtering use cases, but the description itself doesn't provide this guidance.

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

Deploy Server

zia_list_cloud_app_policy

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools