litespeed/list-cache-exclusions reads all six cache exclusion lists in one call: URIs, categories, tags, cookies, user agents and roles.
It also returns the forced-cache and forced-private URI lists and the dropped query strings, which are the same mechanism pointed the other way.
At a glance
| Ability | litespeed/list-cache-exclusions |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Exclusions accumulate. A checkout URI excluded during a payment integration, a cookie added while debugging, a role excluded years ago for a reason nobody remembers — and each one is a set of pages permanently paying full server cost.
Reading them together is the only way to see that. Individually each entry looks reasonable; the pattern only shows when you can see all six lists at once.
The forced lists are the inverse and deserve equal attention: a URI forced into the cache that should not be is the leak direction rather than the slow direction.
Dropped query strings are worth understanding too — they let LiteSpeed treat ?utm_source=x as the same page as the bare URL, which is usually exactly right and occasionally hides a parameter that genuinely changes the page.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What is excluded from the LiteSpeed cache on this site?
It resolves to one call:
{
"ability": "litespeed/list-cache-exclusions",
"parameters": {}
}Worth knowing
- Old exclusions are the most common reason a site is slower than its cache settings suggest.
- The forced lists are the same mechanism in reverse, and carry the leak risk.
- Dropped query strings improve the hit rate but can flatten a parameter that matters.
Related abilities
- Update Cache Exclusions — change one list
- Get Cache Settings — the whole cache picture
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category