consent/update-consent-settings changes a consent setting. It accepts a named list of settings, not arbitrary keys.
That narrowness is the design, not a gap.
At a glance
| Ability | consent/update-consent-settings |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Configuration |
| Requires | CookieYes, 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 it is not a general settings writer
The setting store holds the account credentials in the same array as the preferences. A general writer over that array is a general writer over the credentials, and the difference between the two is a key name — which is a thin thing to rely on when the caller is an assistant working from a sentence.
So the accepted inputs are enumerated. Anything not on the list is refused, and adding to the list is a deliberate act rather than a consequence of the store growing.
Which privacy law the site answers to is not on the list either, for a different reason. That is a legal judgement about the site owner’s situation — where their visitors are, what they do with the data — and it belongs to them, not to whatever was inferred from a request.
Consent record keeping is on the list, with a caveat: turning it on requires a linked account, because there is no local table for the records.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
consent_log_status | boolean | No | Whether consent records are kept. Recording them requires a linked account. |
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | The settings after the write. |
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:
Turn on consent record keeping.
It resolves to one call:
{
"ability": "consent/update-consent-settings",
"parameters": {
"consent_log_status": true
}
}Worth knowing
- Idempotent.
- Requires a linked account for record keeping to do anything.
- The privacy law the banner answers to is not changeable here, by design.
- Credentials in the same store are never writable through this.
Related abilities
- Get Consent Settings — read the current state
- Get Consent Statistics — what record keeping produces
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category