> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/how-to/view-policy-of-all-your-web-applications-apis.md).
# View Policy of all your Web Applications/APIs
A summary of all CloudGuard WAF practices is available under **Policy->Policy** in the form of rules view.
### Rules table
#### Asset/Zone
The asset or zone (dynamic group of assets) the security practice protects
#### Practices
The CloudGuard WAF practice configured to protect the asset/zone.
#### Mode
The mode can be show:
* **Detect** - The practice is configured to log events without blocking traffic.
* **Prevent** - The practice is configured to block incoming traffic upon detection of a malicious attack.
* **Disabled**
* **Mixed** - The practice may be set to "Detect" or "Prevent" but a mode of at least one sub-practice (e.g. CloudGuard WAF IPS, API Schema Validation, etc.) is set to override the main mode.
#### Exceptions
Shows configured exclusions configured for the practice.
#### Triggers
Shows the Log Trigger object/s configured for the practice.
#### Enforcement
Shows the Agents Profile/s that enforce this rule.
### Agent View
The agents table reflects the policy number used by each agent, and can be used to monitor policy updates and any errors.
### Tab view
When selecting a rule, the bottom tabs will show the data of the asset/zone the rule protects.
* The "Attribute" tab shows a summary of the asset/zone data.
* The other tabs are the same tabs shown when editing the asset/zone object and can be used to edit the asset and practice configuration without being required to go to either the Assets or Zones.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://waf-doc.inext.checkpoint.com/how-to/view-policy-of-all-your-web-applications-apis.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.