store/get-store-settings reads the general store settings: address and country, currency and price formatting, weight and dimension units, stock management and its thresholds, guest checkout, and whether tax is calculated.
It is a deliberately narrow list.
At a glance
| Ability | store/get-store-settings |
| Toolset | WooCommerce — toolset/woocommerce |
| Group | WooCommerce › Store Configuration |
| Requires | WooCommerce, 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
WooCommerce keeps hundreds of options under the same prefix, and among them is every payment gateway’s configuration — API keys, secrets, webhook tokens. A general reader over that prefix is a credential dump waiting for somebody to ask the wrong question.
So the readable set is enumerated. Everything on it is a general store setting; nothing on it is a credential; and growing the list is a deliberate act rather than something that happens when a plugin adds an option.
The settings that are here are the ones that explain a shop’s behaviour: the currency and its formatting, whether tax is calculated at all, whether guests can check out, what the stock thresholds are.
That last group is worth reading before any inventory work — the low-stock and out-of-stock thresholds decide when a product is hidden from the catalogue.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | The readable settings, by name. |
note | string | A statement of what is deliberately not readable here. |
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 this store configured?
It resolves to one call:
{
"ability": "store/get-store-settings",
"parameters": {}
}Worth knowing
- Payment gateway configuration is not readable here, by design.
- The stock thresholds decide when products are hidden from the catalogue.
- Tax calculation being off makes every tax rate on the store inert.
Related abilities
- Update Store Settings — change what is changeable
- Get Tax Rates — the tax side in detail
- Get Store Status — which gateways are enabled
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category