List Firewall Policies
List the WAF/firewall policies on the calling user's account. Firewall policies are evaluated before traffic policies — a request blocked by the firewall never reaches the agent. Each policy has an action (allow or block) and a list of conditions; if all conditions match, the action fires.
Policies are evaluated in priority order (lower first). The first matching policy determines the verdict; subsequent policies are skipped (allow-list / block-list semantics).
Distinct from traffic policies: firewall policies are account-wide and binary (allow/block), while traffic policies attach per-endpoint and can do rich actions (rate limit, redirect, transform).
Query parameters
true) or disabled (false) policies. Omit for all.true — each policy carries its full conditions array. Set false to omit conditions for a lighter response.page returns the full set. When page is supplied without page_size, default page size applies; capped at 200. When paginated, the response object also carries total, page, and page_size.Response (200 OK)
A JSON object {"policies": [...]} (ordered by priority ASC). Each policy:
allow or block. allow stops further policy evaluation and lets the request through; block rejects (HTTP 403 by default, or the account's custom firewall error template if active).100.false skips this policy at evaluation time.include_conditions=false). A policy with zero conditions matches every request (use carefully). Each condition: {id, policy_id, condition_type, operator, condition_value, logical_operator, created_at}.last_matched is null if never matched in-window; hits_daily is a per-day series (index 0 = oldest).The top-level response object may also include a posture summary (account-level firewall stats) alongside policies.