Redirection does more than hold rules. It can watch for post slug changes and create redirects automatically, expire old ones, and log every hit — and knowing how it is set up explains a lot of its behaviour.
redirects/get-settings returns Redirection’s settings, with one deliberate omission: the REST API token is never included.
At a glance
| Ability | redirects/get-settings |
| Toolset | Redirection — toolset/redirection |
| Group | Redirection |
| Requires | Redirection, 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.43 and later |
How it works
It reports whether Redirection auto-creates a redirect when a post slug changes, how long logs and 404s are kept, what it logs, how it handles HTTP headers and https, and which modules are active — everything except the API token.
Input
None. It takes no parameters.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | Redirection’s settings, with the REST API token removed. |
success | boolean | Whether the call completed. |
message | string | A one-line summary suitable for showing a human. |
Example
Ask your assistant:
Is Redirection set to auto-create redirects when a post slug changes?
It resolves to one call:
{
"ability": "redirects/get-settings",
"parameters": {}
}Worth knowing
- Read-only — it reads the settings and writes nothing.
- The REST API token is never returned; it authenticates write access to the whole redirect table.
- Needs the Redirection plugin active; without it you get a clear “not active” message.
Related abilities
- List Redirect Hit Log — see the hits logging records
- List Redirects — the redirects those settings govern
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category