Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zia_list_cloud_app_control_rules

Read-only

List ZIA Cloud App Control rules for a category.

Instructions

List ZIA Cloud App Control rules for a category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional 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.
rule_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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 / rule_type / title
      Added value: +"Rule Type"
    • addedInput schema / title
      Added value: +"zia_list_cloud_app_control_rulesArguments"
  2. Changed8 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / query / description
      Previous value: -"JMESPath expression for client-side filtering/projection of results."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 / rule_type / description
      Removed value: -"Required. The CAC rule category to list. 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 / rule_type / title
      Removed value: -"Rule Type"
    • removedInput schema / properties / search
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Optional server-side substring filter on rule name.",
      -  "title": "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_control_rulesArguments"
  3. First observedv0.12.7

TDQS

C2.3/5.0
Behavior1/5

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

The description adds no behavioral details beyond the annotations (readOnlyHint, openWorldHint). It does not mention side effects, permissions, limits, or output format.

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 concise and to the point, utilizing a single sentence. It is not verbose, though it omits necessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the schema has two parameters and no output description, the tool description is incomplete. It does not explain the return structure or the meaning of 'rule_type', making it insufficient for a user to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool description does not explain parameters. While the schema documents 'query' (JMESPath), the required 'rule_type' is left undefined, and the description offers no clarification about either parameter.

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 clearly states the action (List), the resource (ZIA Cloud App Control rules), and the scope (for a category). It is distinguishable from other list tools, though 'category' is somewhat ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool over alternatives. It does not mention related tools like zia_get_cloud_app_control_rule or zia_list_cloud_app_policy, nor does it clarify when 'for a category' applies.

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

Deploy Server

Other Tools