consent/get-consent-settings reads the consent configuration: whether the banner is on, what languages it is offered in, whether consent records are being kept, and whether this site is linked to a consent account.
Credentials stored alongside those settings are never returned, and anything withheld is listed so an empty setting can be told apart from a hidden one.
At a glance
| Ability | consent/get-consent-settings |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Configuration |
| Requires | CookieYes, 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
The settings store holds the account credentials next to ordinary preferences. Returning the store wholesale would hand out API keys along with the language list, so the credentials are filtered out.
Filtering silently would be worse than useless, though: a caller cannot tell whether a key is missing because nothing was configured or because something was hidden. So the withheld keys are named in a redacted list. You learn that a credential exists without receiving it.
The connected flag is the one that explains most surprises in this suite. Four of the reporting abilities have nothing to return without it, and consent records cannot be kept without it either.
The onboarding step is included because a half-finished setup is a common state, and it is the field that says how far through it the site got.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
connected | boolean | Whether the site is linked to a consent account. |
banner_enabled | boolean | Whether the banner is switched on. |
consent_log_status | boolean | Whether consent records are being kept. |
default_language | string | The fallback language. |
selected_languages | array | The languages the banner is offered in. |
plan | object | The plan the linked account is on, when connected. |
redacted | array | The setting keys whose values were withheld. |
onboarding_step | string | How far through setup the site is. |
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:
How is cookie consent set up on this site?
It resolves to one call:
{
"ability": "consent/get-consent-settings",
"parameters": {}
}Worth knowing
- A key in
redactedexists and has a value. A key that is absent was never set. connectedfalse explains why the reporting abilities return nothing.- Nothing in this suite links an account. That is done on the plugin’s own screen.
Related abilities
- Update Consent Settings — change what can be changed
- Get Banner Status — what visitors receive
- List Banner Languages — the language list in detail
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category