litespeed/update-cache-exclusions changes one cache exclusion list: add to it, remove from it, or replace it.
The mode is what makes this safe to use from an assistant.
At a glance
| Ability | litespeed/update-cache-exclusions |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Page Cache |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Why add and remove exist at all
The obvious API for a list is “here is the new list”. It is also the one that loses entries: to add a line you must first read the list, append, and write the whole thing back — and any entry added between the read and the write is gone, along with any entry the caller did not think to include.
With add and remove, adding one exclusion is one call that touches one line. Nothing else in the list is in play.
The types cover the six lists plus the forced and query-string ones: uri, category, tag, cookie, user-agent, role, force-uri, force-public-uri, private-uri and drop-query-string.
Excluding a URI is the standard fix for a page that must not be cached — a checkout, a live dashboard, anything that renders per request. It is also the standard over-reaction to a caching bug, so prefer the narrowest exclusion that works.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
type | string | Yes | Which list: uri, category, tag, cookie, user-agent, role, force-uri, force-public-uri, private-uri or drop-query-string. |
values | array | Yes | The entries to add, remove or set. |
mode | string | No — defaults to add | add, remove or replace. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
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:
Stop caching the checkout page.
It resolves to one call:
{
"ability": "litespeed/update-cache-exclusions",
"parameters": {
"type": "uri",
"values": ["/checkout"],
"mode": "add"
}
}Worth knowing
- Use
addandremoverather thanreplaceunless you really mean to set the whole list. - Prefer the narrowest exclusion that fixes the problem.
- Purge after excluding a URI — the old cached copy is still there until you do.
- Idempotent in every mode.
Related abilities
- List Cache Exclusions — read all the lists first
- Purge URLs — clear the page you just excluded
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category