consent/get-scan-status reads when the site was last scanned for cookies, whether the scan succeeded, and the plan limits in force.
The scan itself runs on the consent service and cannot be started from here.
At a glance
| Ability | consent/get-scan-status |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Reporting |
| 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 scan is what keeps the declared inventory honest. It crawls the site, observes what cookies are actually set, and adds what it finds. Without it the inventory is whatever somebody typed in, and it drifts every time a new tag or embed is added.
So the last-scan date is a claim about how current the disclosure is. Three months and two new marketing tools later, the banner is describing a site that no longer exists.
These figures are not kept on this site. There is no local table for them: the consent service records them and this reads them back, which means the site has to be linked to a consent account for there to be anything to read. Nothing here links an account — that is done on the plugin’s own screen.
Without an account the inventory is maintained by hand, through consent/add-cookie — which works, but nothing then tells you what you missed.
The plan limits come back alongside, because scan frequency and page count are usually where a plan binds first.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
scans | array | Recent scans with their dates and outcomes. |
plan | object | The plan limits that apply to scanning. |
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:
When was this site last scanned for cookies?
It resolves to one call:
{
"ability": "consent/get-scan-status",
"parameters": {}
}Worth knowing
- Scanning cannot be started from this suite.
- Needs a linked consent account.
- A stale scan means the declared inventory may be missing recent additions.
- Without an account, maintain the inventory by hand and expect gaps.
Related abilities
- List Declared Cookies — what the last scan left you with
- Declare a Cookie — fill a gap by hand
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category