consent/delete-cookie removes a cookie from the declared list. It refuses without confirm: true.
The cookie itself is unaffected. This only stops the banner telling visitors about it.
Before you run it
This removes a disclosure, not a cookie. If the site still sets the cookie, the banner now fails to mention it — the removal makes the disclosure less accurate, not more. The text stored for it in every language goes with it, and there is no undo.
At a glance
| Ability | consent/delete-cookie |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Declared Cookies |
| Requires | CookieYes, active on the site |
| Capability | manage_options |
| Safety | Destructive — removes a disclosure, and refuses to run without confirm: true. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Most destructive operations remove something the site was doing. This one removes something the site was saying, and the thing it was saying might have been true.
A declaration that no longer matches reality is a problem in exactly one direction: an entry for a cookie the site stopped setting is untidy, while a missing entry for a cookie the site still sets is the gap a regulator cares about. Deleting moves you toward the second kind.
So the confirmation is not about recoverability — the entry is small and easy to recreate. It is about making sure the deletion was the request, and not a tidy-up of a list that looked too long.
Every language’s description and duration for this cookie goes with the entry.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | Cookie ID, from consent/list-cookies. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | boolean | Whether the entry was removed. |
banner_refreshed | boolean | Whether the cached banner was rebuilt after the write. This is the field that says the change actually reached visitors. |
languages | array | The languages the banner is built for. |
rendered | object | The size of the built banner, per language. |
pending_rebuild | boolean | Whether the banner is still waiting to be rebuilt. True after a write means the change is stored but not yet being served. |
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:
Remove the declaration for a cookie we no longer set.
It resolves to one call:
{
"ability": "consent/delete-cookie",
"parameters": {
"id": 41,
"confirm": true
}
}Worth knowing
- Confirm the site really stopped setting the cookie before removing its entry.
- No undo. Re-declaring means retyping every language.
- The banner is rebuilt afterwards; the response says whether that succeeded.
Related abilities
- Get Declared Cookie — read it before you remove it
- Declare a Cookie — put it back
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category